hadoop-common-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Aaron T. Myers (Commented) (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HADOOP-8077) HA: fencing method should be able to be configured on a per-NN or per-NS basis
Date Fri, 06 Apr 2012 02:10:24 GMT

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

Aaron T. Myers commented on HADOOP-8077:

Patch looks pretty good to me, Todd. One small comment. +1 once this is addressed.

# In TestDFSHAAdmin#testFencingConfigPerNameNode, how about actually asserting that the default
fencer which should succeed actually does succeed, before asserting that the fencer fails
when set with an NN-specific fencer.
> 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


View raw message