[
https://issues.apache.org/jira/browse/HDFS-3507?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13438539#comment-13438539
]
Vinay commented on HDFS-3507:
-----------------------------
Thanks Aaron for your inputs.
{quote}The new parameter in the SetSafeModeRequestProto should be marked
optional, defaulted to false, to maintain compatibility{quote}
Got it.
{quote}Seems like the calls in DFSAdmin should be passing "true" for isChecked,
so that the the active NN is used.{quote}
I think this also similar one to HDFS-3744, may be this we can take up in
separate Jira or HDFS-3744 itself. In current patch I am just passing "false"
to maintain previous behaviour.
I agree with your opinion about setting the HDFS service to safemode instead of
setting it to only one NN.
> 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.1.0-alpha, 3.0.0
> Reporter: Vinay
> Assignee: Vinay
> Priority: Critical
> Attachments: 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:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
