increase inode reuse delay from 1 day to 30 days #492
Conversation
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
|
It also potentially increases memory usage of your master server. What kind of inode reuse issues did you encounter? Maybe the problem is somewhere else, not precisely in master and inode management. |
|
And the most important detail: which release caused the problem? |
|
This patch was initially applied to 2.5.4 a couple years ago when we switched from MooseFS. I believe the issue was as follows: A directory is unlinked, but still open. After a day, the master reuses the inode, and the mount which still has the old directory open tries to access this inode which was reused too soon. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Increase inode reuse delay from 1 day to 30 days. This makes it much harder to run into inode reuse issues, as I did in my cluster.