HDFS-17780. The retry logic in IncrementalBlockReport may bypass the configured IBR interval, causing contention on NameNode #7681
+2
−3
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.
Description of PR
As described in HDFS-17780, the retry logic in sendIBR() can bypass the configuration of
dfs.blockreport.incremental.intervalMsec
and cause the IBR to be sent with every heartbeat.The fix updates the IBR timestamp every time the RPC is called.
How was this patch tested?
No test needed.
For code changes:
LICENSE
,LICENSE-binary
,NOTICE-binary
files?