[
https://issues.apache.org/jira/browse/HDFS-17313?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
huangzhaobo99 updated HDFS-17313:
---------------------------------
Description:
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)
*Sample outputs*
{code:java}
$ 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.{code}
was:
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 principle*
# 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)
*Sample outputs*
{code:java}
$ 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.{code}
> dfsadmin -reconfig option to start/query reconfig on all live namenodes.
> ------------------------------------------------------------------------
>
> Key: HDFS-17313
> URL: https://issues.apache.org/jira/browse/HDFS-17313
> Project: Hadoop HDFS
> Issue Type: New Feature
> Reporter: huangzhaobo99
> Assignee: huangzhaobo99
> Priority: Major
> Labels: pull-request-available
>
> 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)
> *Sample outputs*
> {code:java}
> $ 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.{code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: hdfs-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: hdfs-issues-h...@hadoop.apache.org
