hadoop-hdfs-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Todd Lipcon (Commented) (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HDFS-3247) Improve bootstrapStandby behavior when original NN is not active
Date Tue, 10 Apr 2012 20:23:17 GMT

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

Todd Lipcon commented on HDFS-3247:
-----------------------------------

I think we could do one of the following:
1) Improve the error message to note that the admin should make sure the other NN is active
before proceeding
2) Have it automatically transition it to active if this is the case.

What do you think? I think 1 makes more sense, since the admin has to make an explicit decision.
                
> Improve bootstrapStandby behavior when original NN is not active
> ----------------------------------------------------------------
>
>                 Key: HDFS-3247
>                 URL: https://issues.apache.org/jira/browse/HDFS-3247
>             Project: Hadoop HDFS
>          Issue Type: Improvement
>          Components: ha
>    Affects Versions: 2.0.0
>            Reporter: Todd Lipcon
>            Assignee: Todd Lipcon
>            Priority: Minor
>
> Currently, if you run bootstrapStandby while the first NN is in standby mode, it will
spit out an ugly StandbyException with a trace. Instead, it should print an explanation that
you should transition the first NN to active before bootstrapping.

--
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