[
https://issues.apache.org/jira/browse/HDFS-15509?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17170330#comment-17170330
]
Leon Gao commented on HDFS-15509:
---------------------------------
Ah, thanks for the pointer [~ayushtkn]! Didn't notice that ticket. Seems like
an interesting discussion there.
I don't really get the reason for the objection that we need to keep both NN in
the same state though..
The sequence of namenodes in the config matters... If nn0 is active then the
command will just work for nn0 regardless of the state of nn1, but if nn1 is
active and nn0 is down this will fail, which is pretty ambiguous : )
Anyways this is a duplicated ticket.
> Set safemode should not fail if one of the namenode is down.
> ------------------------------------------------------------
>
> Key: HDFS-15509
> URL: https://issues.apache.org/jira/browse/HDFS-15509
> Project: Hadoop HDFS
> Issue Type: Improvement
> Components: hdfs
> Affects Versions: 3.3.0
> Reporter: Leon Gao
> Assignee: Leon Gao
> Priority: Minor
> Attachments: HDFS-15509.patch
>
>
> When the first namenode (let's say nn0) is down, set safemode command will
> always fail unless users manually update the configuration. This is
> distracting when debugging issues.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: hdfs-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: hdfs-issues-h...@hadoop.apache.org
