hadoop-hdfs-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Rajiv Chittajallu (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HDFS-2231) Configuration changes for HA namenode
Date Sun, 07 Aug 2011 01:29:27 GMT

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

Rajiv Chittajallu commented on HDFS-2231:

Rather than having to xmlinclude a separate file with the NN's ID, can we allow the user to
just use the local hostname? eg set the default to $\{env.hostname\} or some such, and have
it get substituted?

Physical hosts serving the primary and backup service might change during the lifetime of
the cluster. Using hostname(1) or hostid(1) might work but it not advisable, in production
sites, as it might require a configuration refresh when the physical host is replaced.

> Configuration changes for HA namenode
> -------------------------------------
>                 Key: HDFS-2231
>                 URL: https://issues.apache.org/jira/browse/HDFS-2231
>             Project: Hadoop HDFS
>          Issue Type: Sub-task
>            Reporter: Suresh Srinivas
>            Assignee: Suresh Srinivas
>             Fix For: HA branch (HDFS-1623)
> This jira tracks the changes required for configuring HA setup for namenodes.

This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira


View raw message