Skip to content
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

make HealthMonitor thresholds configurable #8556

Closed
rymsha opened this issue Dec 15, 2020 · 1 comment · Fixed by #10321
Closed

make HealthMonitor thresholds configurable #8556

rymsha opened this issue Dec 15, 2020 · 1 comment · Fixed by #10321
Assignees
Labels
Milestone

Comments

@rymsha
Copy link
Contributor

rymsha commented Dec 15, 2020

There might be cases when heap usage is constantly high on data nodes, but performance is acceptable.
Suspicions Hazelcast HealthMonitor messages may be confusing and thresholds heap usage thresholds can be safely increased

@rymsha rymsha self-assigned this Dec 15, 2020
@rymsha rymsha added this to the 7.13.4 milestone Nov 3, 2023
@rymsha
Copy link
Contributor Author

rymsha commented Nov 3, 2023

The default value of system.hazelcast.health.monitoring.threshold.memory.percentage = 90 should be different from HZ hazelcast.health.monitoring.threshold.memory.percentage = 70, because modern GCs are very lazy and cause a lot of needless messages in the logs

@rymsha rymsha linked a pull request Nov 3, 2023 that will close this issue
rymsha added a commit that referenced this issue Nov 3, 2023
@jsi jsi added Bug and removed Improvement labels Nov 6, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants