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

Assume all swap memory is free on values overflow #9383

Merged
merged 4 commits into from
Dec 6, 2018

Conversation

jsoriano
Copy link
Member

@jsoriano jsoriano commented Dec 4, 2018

There have been reports about user swap memory being a value that looks
like an overflow. At the moment used swap memory is calculated as the
value of total memory minus the free memory, so this means that free
memory is bigger than total in some cases. This isn't possible in
principle. Assume that no swap is being used if that happens.

Closes #6271

There have been reports about user swap memory being a value that looks
like an overflow. At the moment used swap memory is calculated as the
value of total memory minus the free memory, so this means that free
memory is bigger than total in some cases. This isn't possible in
principle. Assume that no swap is being used if that happens.
@jsoriano jsoriano added module review libbeat Metricbeat Metricbeat Team:Integrations Label for the Integrations team labels Dec 4, 2018
@jsoriano jsoriano self-assigned this Dec 4, 2018
@elasticmachine
Copy link
Collaborator

Pinging @elastic/infrastructure

@jsoriano jsoriano added the needs_backport PR is waiting to be backported to other branches. label Dec 4, 2018
@@ -38,6 +38,7 @@ https://github.com/elastic/beats/compare/v7.0.0-alpha1...master[Check the HEAD d
- Fix autodiscover configurations stopping when metadata is missing. {pull}8851[8851]
- Log events at the debug level when dropped by encoding problems. {pull}9251[9251]
- Refresh host metadata in add_host_metadata. {pull}9359[9359]
- Handle cases of free swap being bigger than total swap by assuming no swap is being used. {issue}6271[6271] {pull}[]
Copy link
Contributor

Choose a reason for hiding this comment

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

You haven't written the pull number. Maybe I'd add the module involved too

@jsoriano
Copy link
Member Author

jsoriano commented Dec 6, 2018

Thanks for the reviews, changes addressed.

Copy link
Contributor

@sayden sayden left a comment

Choose a reason for hiding this comment

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

LGTM

Copy link
Member

@ruflin ruflin left a comment

Choose a reason for hiding this comment

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

LGTM. Just minor comment on the log message. Stumbled over the Odd part.

Co-Authored-By: jsoriano <jaime.soriano@elastic.co>
@jsoriano jsoriano merged commit 7d9b2e3 into elastic:master Dec 6, 2018
@jsoriano jsoriano deleted the swap-overflow branch December 6, 2018 15:17
jsoriano added a commit to jsoriano/beats that referenced this pull request Dec 6, 2018
There have been reports about user swap memory being a value that looks
like an overflow. At the moment used swap memory is calculated as the
value of total memory minus the free memory, so this means that free
memory is bigger than total in some cases. This isn't possible in
principle. Assume that no swap is being used if that happens.

(cherry picked from commit 7d9b2e3)
@jsoriano jsoriano added v6.6.0 and removed needs_backport PR is waiting to be backported to other branches. labels Dec 6, 2018
jsoriano added a commit that referenced this pull request Dec 10, 2018
There have been reports about user swap memory being a value that looks
like an overflow. At the moment used swap memory is calculated as the
value of total memory minus the free memory, so this means that free
memory is bigger than total in some cases. This isn't possible in
principle. Assume that no swap is being used if that happens.

(cherry picked from commit 7d9b2e3)
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 this pull request may close these issues.

4 participants