You are viewing a plain text version of this content. The canonical link for it is here.
Posted to hdfs-issues@hadoop.apache.org by "He Xiaoqiao (JIRA)" <ji...@apache.org> on 2019/03/10 16:39:00 UTC
[jira] [Updated] (HDFS-14351) RBF: Optimize configuration item
resolving for monitor namenode
[ https://issues.apache.org/jira/browse/HDFS-14351?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
He Xiaoqiao updated HDFS-14351:
-------------------------------
Summary: RBF: Optimize configuration item resolving for monitor namenode (was: Optimize configuration item resolving for monitor namenode)
> RBF: Optimize configuration item resolving for monitor namenode
> ---------------------------------------------------------------
>
> Key: HDFS-14351
> URL: https://issues.apache.org/jira/browse/HDFS-14351
> Project: Hadoop HDFS
> Issue Type: Sub-task
> Components: rbf
> Reporter: He Xiaoqiao
> Assignee: He Xiaoqiao
> Priority: Major
>
> We invoke {{configuration.get}} to resolve configuration item `dfs.federation.router.monitor.namenode` at `Router.java`, then split the value by comma to get nsid and nnid, it may confused users since this is not compatible with blank space but other common parameters could do. The following segment show example that resolve fails.
> {code:java}
> <property>
> <name>dfs.federation.router.monitor.namenode</name>
> <value>nameservice1.nn1, nameservice1.nn2</value>
> <description>
> The identifier of the namenodes to monitor and heartbeat.
> </description>
> </property>
> {code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: hdfs-issues-unsubscribe@hadoop.apache.org
For additional commands, e-mail: hdfs-issues-help@hadoop.apache.org