-
Notifications
You must be signed in to change notification settings - Fork 146
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
Show scylla_sstables_bloom_filter_memory_size
on one of the dashboards
#2219
Comments
@michoecho can you also suggest an alert based on that? |
@michoecho can you look at the memory metrics you put, it's the same one |
@avikivity @denesb @mykaul What do you think? Should we have an alert if bloom filters exceed some fraction of memory? And if yes, what should be the threshold? |
yes
I think it's a reasonable starting point. |
I've asked @d-helios to scan our cloud to see where we are at right now, I think based on the results we can determine the alert threshold |
@michoecho ping, please look at the metric you put, one is missing |
If you mean the fact that I typed
then the answer is that I meant
Otherwise I don't understand what you are asking for. |
@michoecho yes, that is exactly what I was asking about |
I've checked the cloud, I think 0.1 is a good threshold |
We saw production nodes OOMing due to bloated bloom filters multiple times lately. (2 times in the last week).
And every time people seem to forget that we have a metric for this, and they waste time e.g. logging into the cluster and
du
ing the bloom filter files.Since the metric proved useful many times, maybe we should put it into one of the dashboards.
Perhaps it should be normalized by total memory. (E.g.
sum by (...) (scylla_sstables_bloom_filter_memory_size) / sum by (...) (scylla_memory_total_memory)
).The text was updated successfully, but these errors were encountered: