[
https://issues.apache.org/jira/browse/HADOOP-7938?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13195343#comment-13195343
]
Todd Lipcon commented on HADOOP-7938:
-------------------------------------
- I don't particularly like that --force-fence has to be the last argument. I'd
expect it could go anywhere.
- Maybe we should add a {{NodeFencer.create(conf)}} call, which would return
null if not configured?
- There's an empty whitespace change in NodeFencer.java
- Maybe add a TODO at the fence-back point which refers to HADOOP-7983?
Would it be simpler if the fail-back call just recursed back into the same
function with the arguments swapped?
> HA: the FailoverController should optionally fence the active during failover
> -----------------------------------------------------------------------------
>
> Key: HADOOP-7938
> URL: https://issues.apache.org/jira/browse/HADOOP-7938
> Project: Hadoop Common
> Issue Type: Sub-task
> Components: ha
> Affects Versions: HA Branch (HDFS-1623)
> Reporter: Eli Collins
> Assignee: Eli Collins
> Fix For: HA Branch (HDFS-1623)
>
> Attachments: hadoop-7938.txt, hadoop-7938.txt
>
>
> The FailoverController in HADOOP-7924 needs to be able to fence off the
> current active in case it fails to transition to standby (or the user
> requests it for sanity). This is needed even for manual failover (the CLI
> should use the configured fencing mechanism). The FC needs to access the
> HDFS-specific implementations HDFS-2179, could add a common fencing interface
> (or just shell out but we may not always want to do that).
--
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
