-
Notifications
You must be signed in to change notification settings - Fork 25.2k
Handle negative free disk space in deciders #48392
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
Merged
DaveCTurner
merged 5 commits into
elastic:master
from
DaveCTurner:2019-10-23-handle-negative-free-space
Oct 23, 2019
Merged
Changes from all commits
Commits
Show all changes
5 commits
Select commit
Hold shift + click to select a range
eaa7bab
Handle negative free disk space in deciders
DaveCTurner 144e0f4
Merge branch 'master' into 2019-10-23-handle-negative-free-space
DaveCTurner 9ea918f
New class to avoid bogus DiskUsage instances
DaveCTurner f5cf7b6
Apparently negative bytes are legit, see DiskUsageTests
DaveCTurner e3c35fd
We can get Long.MAX_VALUE for the free space so must be careful doing…
DaveCTurner File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
How could this overflow?
Isn't
relocatingShardSize >= 0
and0 <= diskUsage.getFreeBytes() <= Long.MAX_VALUE
? Is this to capture the case wherediskUsage.getFreeBytes() == 0 && relocatingShardSize == Long.MAX_VALUE
?There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
No,
relocatingShardSize
is the net size of all relocations, i.e. shards in minus shards out, so can indeed be negative :(