You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Feb 18, 2021. It is now read-only.
Following an update a couple of by @kirg days ago I'm confused about this value.
This can be configured by setting: ./cherami-admin --env=prod --hostport=fehost2:4922 cfg set cherami-storehost.*.*.*.minFreeDiskSpaceBytes 10000000 and defaults to 40GB.
I've noticed too that the storagemonitor has now hardcoded thresholds of:
Why is the placement threshold set below the threshold for storage hosts to become read only, why is it such large values and is there any way we can affect the monitor's thresholds?
I test cherami locally on my machine with Docker, and ony my mac docker's default overlay disk size is 63GB, and theres probably only about 32GB of that free - this was fine as I used to hop on, and change the minFree to 1gb, so I could carry on testing. Now it doesn't seem like I can do that anymore, as the storehosts all become readonly.
In production we use cherami as a distributed message queue and don't expect more than 20minutes of messages to be backed to disk at any one time, which is no way near the 50GB limit.
Cheers,
Dan
The text was updated successfully, but these errors were encountered:
doodle-tnw
changed the title
What's the point of MinFreeDiskSpaceBytes?
Is MinFreeDiskSpaceBytes still relevant?
Nov 22, 2017
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Following an update a couple of by @kirg days ago I'm confused about this value.
This can be configured by setting:
./cherami-admin --env=prod --hostport=fehost2:4922 cfg set cherami-storehost.*.*.*.minFreeDiskSpaceBytes 10000000
and defaults to 40GB.I've noticed too that the storagemonitor has now hardcoded thresholds of:
Why is the placement threshold set below the threshold for storage hosts to become read only, why is it such large values and is there any way we can affect the monitor's thresholds?
I test cherami locally on my machine with Docker, and ony my mac docker's default overlay disk size is 63GB, and theres probably only about 32GB of that free - this was fine as I used to hop on, and change the minFree to 1gb, so I could carry on testing. Now it doesn't seem like I can do that anymore, as the storehosts all become readonly.
In production we use cherami as a distributed message queue and don't expect more than 20minutes of messages to be backed to disk at any one time, which is no way near the 50GB limit.
Cheers,
Dan
The text was updated successfully, but these errors were encountered: