-
Notifications
You must be signed in to change notification settings - Fork 3.3k
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
HBASE-27629 Let lock wait timeout to improve performance of SnapshotHFileCleaner #5020
Conversation
…FileCleaner Backport of HBASE-27043
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.
confirmed the change as same as 1aa07d5 , please free feel to merge once the precommit passes
🎊 +1 overall
This message was automatically generated. |
@@ -97,6 +98,8 @@ Collection<String> filesUnderSnapshot(final FileSystem fs, final Path snapshotDi | |||
private ImmutableMap<String, SnapshotDirectoryInfo> snapshots = ImmutableMap.of(); | |||
private final Timer refreshTimer; | |||
|
|||
private static final int LOCK_TIMEOUT_MS = 30000; |
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.
Should we make it configurable? Just asking, I'm neutral on whether to introduce a configuration.
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.
After HBASE-27590 I don't think it is necessary because the locking time is drastically reduced. Earlier I have seen the Failed to acquire write lock on taking snapshot after waiting 60000ms
WARN messages continuously on this cluster.
💔 -1 overall
This message was automatically generated. |
💔 -1 overall
This message was automatically generated. |
🎊 +1 overall
This message was automatically generated. |
The |
Backport of HBASE-27043