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

Cherry-pick #9383 to 6.x: Assume all swap memory is free on values overflow #9422

Merged
merged 1 commit into from
Dec 10, 2018

Conversation

jsoriano
Copy link
Member

@jsoriano jsoriano commented Dec 6, 2018

Cherry-pick of PR #9383 to 6.x branch. Original message:

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.

(cherry picked from commit 7d9b2e3)
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 Fail seems to be a timeout

@jsoriano jsoriano merged commit 6997f56 into elastic:6.x Dec 10, 2018
@jsoriano jsoriano deleted the backport_9383_6.x branch December 10, 2018 10:55
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.

2 participants