Dremio V2 helm chart cannot adjust executor db/fs cache pctQuota

1

Hi Team,

I am using the dremio v2 helm chart to deploy to kubernetes. The experience is great.

However, I notice that the my directory /opt/dremio/cloudcache/c0/cm/fs is quickly piling up.

dremio@dremio-executor-0:/opt/dremio$ ls cloudcache/c0/cm/fs
000000	000006	000012	000018	000024	000030	000036	000042	000048	000054	000060	000066	000072	000078	000084	000090	000096	000102	000108	000114	000120	000126
000001	000007	000013	000019	000025	000031	000037	000043	000049	000055	000061	000067	000073	000079	000085	000091	000097	000103	000109	000115	000121	000127
000002	000008	000014	000020	000026	000032	000038	000044	000050	000056	000062	000068	000074	000080	000086	000092	000098	000104	000110	000116	000122	boostedSubDir
000003	000009	000015	000021	000027	000033	000039	000045	000051	000057	000063	000069	000075	000081	000087	000093	000099	000105	000111	000117	000123
000004	000010	000016	000022	000028	000034	000040	000046	000052	000058	000064	000070	000076	000082	000088	000094	000100	000106	000112	000118	000124
000005	000011	000017	000023	000029	000035	000041	000047	000053	000059	000065	000071	000077	000083	000089	000095	000101	000107	000113	000119	000125
dremio@dremio-executor-0:/opt/dremio$ ls cloudcache/c0/cm/fs

I notice that there’s the setting here which control the percentage quota for fs and db used by the executor as cache , namely pctquota.fs and pctquota.db`.

I modified my local copy to expose these two configurations in .values YAML file, currently set to 50 percent.

Can it be exposed in the public helm chart as well?

Curiously, I notice that in the dremio v1 helm chart, it actually exists already.

2

@Ken Yes 70 is the defaul, i will put a change internally to move down the threshold

3

I mean, for the V1 Dremio helm chart, yes, it looks like the default is 70, and it is adjustable via the values.yaml file.

For V2 Dremio Helm chart, it is hardcoded to 100 and it is not adjustable via values.yaml file.

For V2 helm chart, is there any plan to expose the config in values.yaml as well?

4

@Ken Working on it, will keep you posted