hadoop-common-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Todd Lipcon (Updated) (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (HADOOP-8077) HA: fencing method should be able to be configured on a per-NN or per-NS basis
Date Thu, 05 Apr 2012 23:28:24 GMT

     [ https://issues.apache.org/jira/browse/HADOOP-8077?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Todd Lipcon updated HADOOP-8077:
--------------------------------

    Attachment: hadoop-8077.txt

Attached patch implements the above and adds a test case. I also took this opportunity to
move the definition of the fencing key out of common into HDFS -- since it's a dfs.ha.* configuration,
it shouldn't be in common. So this is a cross-project patch.
                
> HA: fencing method should be able to be configured on a per-NN or per-NS basis
> ------------------------------------------------------------------------------
>
>                 Key: HADOOP-8077
>                 URL: https://issues.apache.org/jira/browse/HADOOP-8077
>             Project: Hadoop Common
>          Issue Type: Improvement
>          Components: ha
>    Affects Versions: 0.24.0
>            Reporter: Todd Lipcon
>            Assignee: Todd Lipcon
>         Attachments: hadoop-8077.txt
>
>
> Currently, the fencing method configuration is global. Given that different nameservices
may use different underlying storage mechanisms or different types of PDUs, it would be preferable
to allow the fencing method configuration to be scoped by namenode or nameservice.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Mime
View raw message