hadoop-hdfs-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Vincent Sheffer (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HDFS-5677) Need error checking for HA cluster configuration
Date Tue, 14 Jan 2014 17:36:51 GMT

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

Vincent Sheffer commented on HDFS-5677:

Yet another option to help HDFS users would be to add a command line option to *hadoop namenode*
(or maybe *hdfs getconf*) that will validate the configuration and provide instructions on
how to fix any problems that are found.

> Need error checking for HA cluster configuration
> ------------------------------------------------
>                 Key: HDFS-5677
>                 URL: https://issues.apache.org/jira/browse/HDFS-5677
>             Project: Hadoop HDFS
>          Issue Type: Improvement
>          Components: datanode, ha
>    Affects Versions: 2.0.6-alpha
>         Environment: centos6.5, oracle jdk6 45, 
>            Reporter: Vincent Sheffer
>            Assignee: Vincent Sheffer
>            Priority: Minor
>             Fix For: 3.0.0, 2.3.0
>         Attachments: HDFS-5677.patch
> If a node is declared in the *dfs.ha.namenodes.myCluster* but is _not_ later defined
in subsequent *dfs.namenode.servicerpc-address.myCluster.nodename* or *dfs.namenode.rpc-address.myCluster.XXX*
properties no error or warning message is provided to indicate that.
> The only indication of a problem is a log message like the following:
> {code}
> WARN org.apache.hadoop.hdfs.server.datanode.DataNode: Problem connecting to server: myCluster:8020
> {code}
> Another way to look at this is that no error or warning is provided when a servicerpc-address/rpc-address
property is defined for a node without a corresponding node declared in *dfs.ha.namenodes.myCluster*.
> This arose when I had a typo in the *dfs.ha.namenodes.myCluster* property for one of
my node names.  It would be very helpful to have at least a warning message on startup if
there is a configuration problem like this.

This message was sent by Atlassian JIRA

View raw message