Skip to content

[7.8] Report used memory as zero when total memory cannot be obtained#56909

Merged
danhermann merged 1 commit intoelastic:7.8from
danhermann:backport_56435_7.8_negative_mem_values
May 18, 2020
Merged

[7.8] Report used memory as zero when total memory cannot be obtained#56909
danhermann merged 1 commit intoelastic:7.8from
danhermann:backport_56435_7.8_negative_mem_values

Conversation

@danhermann
Copy link
Copy Markdown
Contributor

We're seeing test failures in 7.x on debian8 (though I have not been able to reproduce them) with negative values for used memory which we compute as total - free. We already coerce both total and free memory to zero if negative values are reported for either because @dakrone's work in #42725 demonstrated that negative values can be returned. That said, it does not appear that those occurrences necessarily coincide such that total may be reported as negative but free is reported as positive thus resulting in a potential free > total situation.

Backport of #56435

@danhermann danhermann added >bug :Core/Infra/Stats Statistics tracking and retrieval APIs backport v7.8.0 labels May 18, 2020
@elasticmachine
Copy link
Copy Markdown
Collaborator

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

@elasticmachine elasticmachine added the Team:Data Management (obsolete) DO NOT USE. This team no longer exists. label May 18, 2020
@danhermann danhermann merged commit afbfac0 into elastic:7.8 May 18, 2020
@danhermann danhermann deleted the backport_56435_7.8_negative_mem_values branch May 18, 2020 13:56
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

backport >bug :Core/Infra/Stats Statistics tracking and retrieval APIs Team:Data Management (obsolete) DO NOT USE. This team no longer exists. v7.8.0

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants