[ https://issues.apache.org/jira/browse/HADOOP-8247?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Todd Lipcon updated HADOOP-8247: -------------------------------- Attachment: hadoop-8247.txt New rev of the patch: - adds a "-forcemanual" flag to the manual failover controller, which allows you to use it even if auto HA is enabled. This is for experts only, and has warnings indicating as much - adds test cases, etc - renames the HARequestInfoProto to HAStateChangeRequestInfoProto, and makes it only apply to the transitionToX() calls. I figure it makes sense to allow the getServiceState/monitorHealth calls to be done by anyone regardless of the HA mode I'll do one more pass of testing and javadoccing tomorrow, but this should mostly be ready to review. > 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