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

Aaron T. Myers commented on HDFS-2914:
--------------------------------------

bq. I am not sure that I completely understand your concern. When active has 
low resources, it goes into safemode. If shared edits goes away, then active 
dies. If you are talking about doing a switchover (active to standby) when 
active is in safemode, I thought I saw a test in testHAsafemode for this 
conditon. If not, I can add a test in a seperate jira.

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.

bq. This is already handled in checkAvailableResources() being called during 
startupCommonServices(). Also, resourcechecker thread is always running and it 
will catch the issue in 5s.

I don't think that's true. {{startCommonServices(...)}} only gets called at NN 
initialization, not on each failover.
                
> 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

        

Reply via email to