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

Do not report negative values for swap sizes #57317

Merged
merged 4 commits into from
May 28, 2020

Conversation

danhermann
Copy link
Contributor

This applies the same fixes for negative memory values in #42725 and #56435 to swap values.

Fixes #57312

@elasticmachine
Copy link
Collaborator

Pinging @elastic/es-core-features (:Core/Features/Monitoring)

@elasticmachine elasticmachine added the Team:Data Management Meta label for data/management team label May 28, 2020
@jakelandis jakelandis added v7.7.2 and removed v7.7.1 labels May 28, 2020
Copy link
Contributor

@jakelandis jakelandis left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@danhermann
Copy link
Contributor Author

@elasticmachine update branch

@danhermann danhermann merged commit b001bab into elastic:master May 28, 2020
@danhermann danhermann deleted the 57312_negative_swap branch May 28, 2020 23:49
danhermann added a commit to danhermann/elasticsearch that referenced this pull request May 28, 2020
danhermann added a commit to danhermann/elasticsearch that referenced this pull request May 29, 2020
danhermann added a commit to danhermann/elasticsearch that referenced this pull request May 29, 2020
@henningandersen
Copy link
Contributor

There is a JDK bug report on this here.

williamrandolph added a commit that referenced this pull request Jun 1, 2021
We've had a series of bug fixes for cases where an OsProbe gives negative
values, most often just -1, to the OsStats class. We added assertions to catch
cases where we were initializing OsStats with bad values. Unfortunately, these
fixes turned to not be backwards-compatible. In this commit, we simply coerce
bad values to 0 when data is coming from nodes that don't have the relevant bug
fixes.

Relevant PRs:
* #42725
* #56435
* #57317

Fixes #73459
williamrandolph added a commit that referenced this pull request Jun 1, 2021
We've had a series of bug fixes for cases where an OsProbe gives negative
values, most often just -1, to the OsStats class. We added assertions to catch
cases where we were initializing OsStats with bad values. Unfortunately, these
fixes turned to not be backwards-compatible. In this commit, we simply coerce
bad values to 0 when data is coming from nodes that don't have the relevant bug
fixes.

Relevant PRs:
* #42725
* #56435
* #57317

Fixes #73459
williamrandolph added a commit that referenced this pull request Jun 1, 2021
We've had a series of bug fixes for cases where an OsProbe gives negative
values, most often just -1, to the OsStats class. We added assertions to catch
cases where we were initializing OsStats with bad values. Unfortunately, these
fixes turned to not be backwards-compatible. In this commit, we simply coerce
bad values to 0 when data is coming from nodes that don't have the relevant bug
fixes.

Relevant PRs:
* #42725
* #56435
* #57317

Fixes #73459
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Monitoring fails to serialize results when free swap is reported as negative
5 participants