-
Notifications
You must be signed in to change notification settings - Fork 23
Switch to using absolute limit for low memory alert #247
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
Nodes with alot of ram can end up triggering this low memory alert even when they have a significant amount of free memory e.g for a node with 512GiB ram, when we hit the current alert (which is con figured to be 80%) we still have 102.5GiB free.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
In commit message: alot -> a lot
Add new line at end of globals.yml
etc/kayobe/kolla/globals.yml
Outdated
es_heap_size: 8g | ||
prometheus_cmdline_extras: "--storage.tsdb.retention.time=30d" | ||
# Threshold to trigger a LowMemory alert in Gibibytes (GiB). When the | ||
# amount of free memory is lower that this value an alert will |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
that -> than
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Done, thanks.
etc/kayobe/kolla/globals.yml
Outdated
# Threshold to trigger a LowMemory alert in Gibibytes (GiB). When the | ||
# amount of free memory is lower that this value an alert will | ||
# be triggered. | ||
alertmanager_low_memory_threshold_gb: 5 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Should we use gib instead of gb?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Good idea, I've changed it.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Good change. Unrelated CI fail. Would be helpful to squash on merge.
we're using RAW statement in the beginning of the file, therefore this change is not enough
|
we could probably add endraw/raw between this new variable @jovial but then, it should probably be a kayobe var, not k-a |
Nodes with alot of ram can end up triggering this low memory alert even when they have a significant amount of free memory e.g for a node with 512GiB ram, when we hit the current alert (which is configured to be 80%) we still have 102.5GiB free.