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] [Commented] (HDFS-3507) DFS#isInSafeMode needs to execute only on Active NameNode
Date Mon, 25 Jun 2012 23:03:44 GMT

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

Aaron T. Myers commented on HDFS-3507:

Hi Vinay, merely marking a patch open/PA again won't trigger another build. You either need
to attach another file (could have the same content) or get someone to kick the HDFS pre-commit
build. I've just done the latter for you.
> 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.1-alpha, 3.0.0
>            Reporter: Vinay
>            Assignee: Vinay
>         Attachments: 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: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira


View raw message