You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
https://issues.apache.org/jira/browse/HDFS-16568 Support batch refreshing of datanode configurations.
There are several nn in the HA or Federated Cluster, and this ticket implements batch refreshing of nn configurations.
Implementation method
Use the DFSUtil.getNNServiceRpcAddressesForCluster method to parse the configuration and obtain the addresses of all nn's
Using two worker threads, currently does not support configuring the number of worker threads (will be implemented in other ticket if necessary)
How was this patch tested?
Add Unit Test.
Sample outputs
$ bin/hdfs dfsadmin -reconfig namenode livenodes start
Started reconfiguration task on node [localhost:50034].
Started reconfiguration task on node [localhost:50036].
Started reconfiguration task on node [localhost:50038].
Started reconfiguration task on node [localhost:50040].
Starting of reconfiguration task successful on 4 nodes, failed on 0 nodes.
$ bin/hdfs dfsadmin -reconfig namenode livenodes status
Reconfiguring status for node [localhost:50034]
SUCCESS: Changed property dfs.heartbeat.interval
From: "5"
To: "3"
Reconfiguring status for node [localhost:50036]
SUCCESS: Changed property dfs.heartbeat.interval
From: "5"
To: "3"
Reconfiguring status for node [localhost:50038]
SUCCESS: Changed property dfs.heartbeat.interval
From: "5"
To: "3"
Reconfiguring status for node [localhost:50040]
SUCCESS: Changed property dfs.heartbeat.interval
From: "5"
To: "3"
Retrieval of reconfiguration status successful on 4 nodes, failed on 0 nodes.
@huangzhaobo99 sorry for the delay in the reply. @tomscut is quite experienced and has helped with the review of the similar changes in the past. Let's wait for his response :)
Sorry that i cannot be of much help.
@huangzhaobo99 sorry for the delay in the reply. @tomscut is quite experienced and has helped with the review of the similar changes in the past. Let's wait for his response :) Sorry that i cannot be of much help.
We're closing this stale PR because it has been open for 100 days with no activity. This isn't a judgement on the merit of the PR in any way. It's just a way of keeping the PR queue manageable.
If you feel like this was a mistake, or you would like to continue working on it, please feel free to re-open it and ask for a committer to remove the stale tag and review again.
Thanks all for your contribution.
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
JIRA: https://issues.apache.org/jira/browse/HDFS-17313
https://issues.apache.org/jira/browse/HDFS-16568 Support batch refreshing of datanode configurations.
There are several nn in the HA or Federated Cluster, and this ticket implements batch refreshing of nn configurations.
Implementation method
How was this patch tested?
Add Unit Test.
Sample outputs