Pruning and fine tuning the BlazeMeter server - Private Cloud

Products

• BlazeMeter

Issue/Introduction

The FS structure holding the data bucket looks like this:

drwx------   2 root root 16384 Nov  8 10:47 lost+found

drwxr-xr-x. 15 root root   201 Nov  8 12:39 ..

drwxr-xr-x   6 root root  4096 Nov  8 12:47 .minio.sys

drwxr-xr-x   9 root root  4096 Feb 25 11:55 data

 

 

Now the data folder seems to be a copy of .minio.sys/buckets/data, which looks like this:

-rw-r--r--     1 root root     272 Nov  8 12:47 policy.json

drwxr-xr-x     3 root root    4096 Nov  8 12:47 ..

drwxr-xr-x     9 root root    4096 Feb 25 11:55 .

drwxr-xr-x     8 root root    4096 Feb 26 15:31 organizations

drwxr-xr-x    11 root root    4096 Mar  3 16:12 collections

drwxr-xr-x 17236 root root 1089536 Mar 16 10:04 sanity

drwxr-xr-x   111 root root    4096 Mar 18 15:17 tests

drwxr-xr-x  2364 root root   98304 Mar 18 15:30 sessions

drwxr-xr-x   351 root root   12288 Mar 18 15:30 masters

drwxr-xr-x     3 root root    4096 Mar 18 17:23 harbors

 

So what I’m saying here is that the subfolder data seems to be a clone of .minio.sys/buckets/data

 

Is there any reason why these two folders need to keep a copy of each other’s structure and contents?

Is it necessary to have noth?

Is it safe to remove the data subfolder at the same level that .minio.sys?

 

What is the safest way to prune the subfolders found under .minio.sys/buckets/data?

Which folders are safe to prune and which ones need to be careful?

 

-rw-r--r--     1 root root     272 Nov  8 12:47 policy.json

drwxr-xr-x     3 root root    4096 Nov  8 12:47 ..

drwxr-xr-x     9 root root    4096 Feb 25 11:55 .

drwxr-xr-x     8 root root    4096 Feb 26 15:31 organizations

drwxr-xr-x    11 root root    4096 Mar  3 16:12 collections

drwxr-xr-x 17236 root root 1089536 Mar 16 10:04 sanity

drwxr-xr-x   111 root root    4096 Mar 18 15:17 tests

drwxr-xr-x  2364 root root   98304 Mar 18 15:30 sessions

drwxr-xr-x   351 root root   12288 Mar 18 15:30 masters

drwxr-xr-x     3 root root    4096 Mar 18 17:23 harbors

 

 

Environment

Release :

Component : BLOCKMASTER

Resolution

Since BlazeMeter is primarily a SaaS offering, support is not exposed to the internal file systems of the product. Nor do we know anything about the intricacies of how data is stored in the S3 bucket. I'm sorry, but your question is beyond the scope of support. I ran your question by one of our Adoption Engineers, which works closely with Private Cloud and Private Location customers, as well as works closely with R&D and Product management, and they don't know enough about the inner workings to answer your question.

Our recommendation is to contact your Broadcom account manager, or bring up this topic to your Adoption Manager during your weekly meetings, and see if they can help find someone in R&D or Product Management that can answer your question. Or, you can look into engaging Professional Services to come in review your systems, and help implement a plan to fine tune your systems, and develop a maintenance plan for your systems.