update current memory usage check on log collector cgroup #2658
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
Systemd cgroup slice somehow gets left behind not cleaned up after logcollector finished. Due to this, max_memory_usage counter not cleaned up for next log collector run. When we check for memory limit, we may get old value and disable the log collector based on that which is not right. So, I updated that logic and consider only memory.stat(RSS+cache+SWAP) to check current memory_usage.
Issue #
PR information
Quality of Code and Contribution Guidelines