HDFS-17106: NameNode can timeout during initialization with dfs.datanode.volumes.replica-add.threadpool.size being 0 #6088
+7
−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
https://issues.apache.org/jira/browse/HDFS-17106
When
dfs.datanode.volumes.replica-add.threadpool.size
is 0, HDFS cluster is never able to start and gets timed out eventually.To reproduce:
dfs.datanode.volumes.replica-add.threadpool.size
to 0mvn surefire:test -Dtest=org.apache.hadoop.hdfs.server.namenode.metrics.TestNameNodeMetrics#testExcessBlocks
This PR improves the description of
replica-add.threadpool.size
inhdfs-default.xml
by sepecifying that it should be positive; the PR also checks whether the value is positive before it is used to initializeaddReplicaThreadPool
.How was this patch tested?
Unit test
For code changes: