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

Hari Mankude commented on HADOOP-8247:
--------------------------------------

Todd,

Can you add tests or verify that FORCEMANUAL option works with automatic 
failover? Specifically, the races to consider are

1. User tries the forcemanual option on NN1 with transitionToActive() when NN1 
is transiting to a standby state (ZKFC1 lost the ephemeral node) and NN2 is 
becomingActive() 
2. User tries the forcemanual option on NN1 with transitionToStandby() when it 
is transiting to an active state.
3. Both these situations when there are other dfsclient threads which are 
posting operations (say mkdir and rmdir) against the active NN.

I don't know if it is possible to test these scenarios with mockito or not.
                
> Auto-HA: add a config to enable auto-HA, which disables manual FC
> -----------------------------------------------------------------
>
>                 Key: HADOOP-8247
>                 URL: https://issues.apache.org/jira/browse/HADOOP-8247
>             Project: Hadoop Common
>          Issue Type: Improvement
>          Components: auto-failover, ha
>    Affects Versions: Auto Failover (HDFS-3042)
>            Reporter: Todd Lipcon
>            Assignee: Todd Lipcon
>         Attachments: hadoop-8247.txt, hadoop-8247.txt
>
>
> Currently, if automatic failover is set up and running, and the user uses the 
> "haadmin -failover" command, he or she can end up putting the system in an 
> inconsistent state, where the state in ZK disagrees with the actual state of 
> the world. To fix this, we should add a config flag which is used to enable 
> auto-HA. When this flag is set, we should disallow use of the haadmin command 
> to initiate failovers. We should refuse to run ZKFCs when the flag is not 
> set. Of course, this flag should be scoped by nameservice.

--
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