HDFS-16275. Enable considerLoad for localWrite #3556
Closed
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
Currently when client is on the same machine of a datanode, it will try to write to the local machine regardless of the load of the datanode, that is the xceiverCount.
In our production cluster, datanode and Nodemanager are running on the same server, so when there are heavy jobs running on a labeled queue, the corresponding datanodes will have higher xceiverCounts than other datanodes. When other clients are trying to write, the exception of "could only be replicated to 0 nodes" would be thrown.
This ticket is to enable considerLoad to avoid the hot local write.
Jira Ticket: https://issues.apache.org/jira/browse/HDFS-16275
How was this patch tested?
unit test
For code changes:
LICENSE,LICENSE-binary,NOTICE-binaryfiles?