[
https://issues.apache.org/jira/browse/HDFS-3071?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Todd Lipcon updated HDFS-3071:
------------------------------
Attachment: hdfs-3071.txt
Here's a patch which addresses the issue. Unfortunately it's cross-project, and
no real way to split it up without breaking one or the other. on commit.
As an experiment, I made the change in such a way that it wouldn't break
protocol compatibility. This resulted in a sort of strange API naming. Let me
know if you think it's better to just break the wire protocol (since we haven't
had an Apache release with HA yet, it's probably acceptable)
> haadmin failover command does not provide enough detail for when target NN is
> not ready to be active
> ----------------------------------------------------------------------------------------------------
>
> Key: HDFS-3071
> URL: https://issues.apache.org/jira/browse/HDFS-3071
> Project: Hadoop HDFS
> Issue Type: Improvement
> Components: ha
> Affects Versions: 0.24.0
> Reporter: Philip Zeyliger
> Assignee: Todd Lipcon
> Attachments: hdfs-3071.txt
>
>
> When running the failover command, you can get an error message like the
> following:
> {quote}
> $ hdfs --config $(pwd) haadmin -failover namenode2 namenode1
> Failover failed: xxx.yyy/1.2.3.4:8020 is not ready to become active
> {quote}
> Unfortunately, the error message doesn't describe why that node isn't ready
> to be active. In my case, the target namenode's logs don't indicate anything
> either. It turned out that the issue was "Safe mode is ON.Resources are low
> on NN. Safe mode must be turned off manually.", but ideally the user would be
> told that at the time of the failover.
--
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
