-
Notifications
You must be signed in to change notification settings - Fork 9.2k
HDFS-16408. Negative LeaseRecheckIntervalMs will let LeaseMonitor loop forever and print huge amount of log #3856
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
Conversation
sodonnel
left a comment
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.
+1 pending good CI run.
|
💔 -1 overall
This message was automatically generated. |
|
@sodonnel |
|
This is fine with no unit tests. I will commit this later as it looks good now. |
thanks for your review. @sodonnel |
(cherry picked from commit e1d0aa9)
(cherry picked from commit e1d0aa9)
(cherry picked from commit e1d0aa9)
Description of PR
Add Preconditions.checkArgument() to ensure the leaseRecheckIntervalMs cannot get set to a value less than or equal to zero.
It avoids negative intervals that cause LeaseMonitor to be in a constant state of fast printing exception logs
JIRA: HDFS-16408
How was this patch tested?
when the configuration item 'dfs.namenode.lease-recheck-interval-ms' is accidentally set to a negative number, origin code will print warning log again and again immediately. This problem can be eliminated after using this patch.