[
https://issues.apache.org/jira/browse/HADOOP-7924?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13180150#comment-13180150
]
Todd Lipcon commented on HADOOP-7924:
-------------------------------------
bq. Think the typo case I mentioned above is worth worrying about or a
non-issue since we let people explicitly transition more than one NN to active
(and have to handle that fallout)?
I think what you said earlier ("Another jira for warning if X is not specified
as one of the options in dfs.ha.namenodes or we add a flag that's required to
failover from a service we can't connect to?") makes sense -- you shouldn't
allow people to specify NNs on this command when they aren't listed in your
config. Another JIRA seems OK, since the cross-project nature is a little
annoying..
>
FailoverController for client-based configuration
> --------------------------------------------------
>
> Key: HADOOP-7924
> URL: https://issues.apache.org/jira/browse/HADOOP-7924
> Project: Hadoop Common
> Issue Type: Sub-task
> Components: ha
> Affects Versions: HA Branch (HDFS-1623)
> Reporter: Eli Collins
> Assignee: Eli Collins
> Attachments: hadoop-7924.txt, hadoop-7924.txt, hadoop-7924.txt
>
>
> Basic FailoverController to coordinate fail-over using a client-based config
> (ie fail-over from NameNode x to NameNode y).
--
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
