HDFS-16559 Seperate IBR thread waiting time from heart beat waiting t… #4233
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.
…ime.
Description of PR
IBR opeeration is seperated from heartbeat thread since HDFS-16016, which is great.
But IBR thread is using the expireTime of heart beat to deside whether wait or not. In a high load DataNode, IBR thread becomes an infinit loop without sleeping and consuming 100% cpu because of the latency of heartbeat reporting.