[
https://issues.apache.org/jira/browse/HDFS-2914?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13207443#comment-13207443
]
Hari Mankude commented on HDFS-2914:
------------------------------------
bq. That's exactly what I'm talking about, but note that TestHASafeMode
doesn't test the case of entering SM because of low resources, which is handled
slightly differently in that the NN won't leave SM automatically as it will
when SM is entered on startup. Seems like we should add a test for this
behavior.
Like I mentioned earlier, I would like to open a seperate test jira for this
issue.
bq. I don't think that's true. startCommonServices(...) only gets called at NN
initialization, not on each failover.
Yep, you are right. Since the thread runs every 5 secs, standby->active will go
into safemode in 5 secs when resources are low. If shared edits is not
available at the time of state transition, active will fail within 5 secs. Let
me try this out and update the jira.
> HA: Standby should not enter safemode when resources are low
> ------------------------------------------------------------
>
> Key: HDFS-2914
> URL: https://issues.apache.org/jira/browse/HDFS-2914
> Project: Hadoop HDFS
> Issue Type: Sub-task
> Components: ha, name-node
> Affects Versions: HA branch (HDFS-1623)
> Reporter: Hari Mankude
> Assignee: Hari Mankude
> Attachments: HDFS-2914-HDFS-1623, HDFS-2914-HDFS-1623,
> HDFS-2914-HDFS-1623.patch, hdfs-2914
>
>
> When shared edits dir is bounced, standby NN is put into safemode by the
> NameNodeResourceMonitor(). However, there is no path for it to exit out of
> safe mode when shared edits dir reappears.
--
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
