hadoop-hdfs-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Aaron T. Myers (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (HDFS-3507) DFS#isInSafeMode needs to execute only on Active NameNode
Date Fri, 16 Nov 2012 22:01:12 GMT

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

Aaron T. Myers updated HDFS-3507:

       Resolution: Fixed
    Fix Version/s: 2.0.3-alpha
     Hadoop Flags: Reviewed
           Status: Resolved  (was: Patch Available)

I've just committed this patch to trunk and branch-2.

Thanks a lot for the contribution, Vinay, and thanks a lot for bearing with my feedback.
> DFS#isInSafeMode needs to execute only on Active NameNode
> ---------------------------------------------------------
>                 Key: HDFS-3507
>                 URL: https://issues.apache.org/jira/browse/HDFS-3507
>             Project: Hadoop HDFS
>          Issue Type: Bug
>          Components: ha
>    Affects Versions: 2.0.2-alpha
>            Reporter: Vinay
>            Assignee: Vinay
>            Priority: Critical
>             Fix For: 2.0.3-alpha
>         Attachments: HDFS-3507.patch, HDFS-3507.patch, HDFS-3507.patch, HDFS-3507.patch
> Currently DFS#isInSafeMode is not Checking for the NN state. It can be executed on any
of the NNs.
> But HBase will use this API to check for the NN safemode before starting up its service.
> If first NN configured is in standby then DFS#isInSafeMode will check standby NNs safemode
but hbase want state of Active NN.

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

View raw message