This changes the EtcdAllocatingTooMuchMemory alerts to use RSS memory rather than working_set.
The reason for this is etcd can use a lot of file cache memory for its file-backed database that will be dropped if it approaches the container's memory limit. This causes this alert to basically be scare-noise, at times. We had a situation where the Go process only had 50MiB of memory resident, but there was 700MiB of file cache memory.
RSS fits better with "AllocatingTooMuch" anyway.
Which issue(s) this PR fixes or relates to
Fixes #
Checklist
[ ] Tests updated.
[ ] Documentation added.
[x] CHANGELOG.md updated - the order of entries should be [CHANGE], [FEATURE], [ENHANCEMENT], [BUGFIX].
What this PR does
This changes the
EtcdAllocatingTooMuchMemoryalerts to use RSS memory rather thanworking_set. The reason for this is etcd can use a lot of file cache memory for its file-backed database that will be dropped if it approaches the container's memory limit. This causes this alert to basically be scare-noise, at times. We had a situation where the Go process only had 50MiB of memory resident, but there was 700MiB of file cache memory.RSS fits better with "AllocatingTooMuch" anyway.
Which issue(s) this PR fixes or relates to
Fixes #
Checklist
CHANGELOG.mdupdated - the order of entries should be[CHANGE],[FEATURE],[ENHANCEMENT],[BUGFIX].about-versioning.mdupdated with experimental features.