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 "J.Andreina (JIRA)" <ji...@apache.org> on 2015/06/24 14:00:06 UTC

[jira] [Commented] (HDFS-4202) Some usage of GetConf tool not compatible with federation

    [ https://issues.apache.org/jira/browse/HDFS-4202?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14599303#comment-14599303 ] 

J.Andreina commented on HDFS-4202:
----------------------------------

Hi [~tlipcon] , i would like to work on this issue. 
Will soon update on this issue.

> Some usage of GetConf tool not compatible with federation
> ---------------------------------------------------------
>
>                 Key: HDFS-4202
>                 URL: https://issues.apache.org/jira/browse/HDFS-4202
>             Project: Hadoop HDFS
>          Issue Type: Bug
>          Components: federation, scripts
>    Affects Versions: 3.0.0, 2.0.2-alpha
>            Reporter: Todd Lipcon
>            Priority: Minor
>
> In the start/stop scripts, we use the "getconf" tool to look up certain config keys to discover hosts we need to start/stop daemons on. However, some of these configs are optionally suffixed by a nameservice or nameservice.namenode identifier. In these cases, the start/stop scripts wouldn't correctly see the configs, and therefore would fail to start all the necessary daemons for the federated cluster.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)