[
https://issues.apache.org/jira/browse/HDFS-15509?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17173420#comment-17173420
]
Ayush Saxena commented on HDFS-15509:
-------------------------------------
Yahh, that is why that Jira couldn't get concluded, There is even a suggestion
there to persist explicit safemode commands in edit log, but that too had
objections, considering that an incompatible change, due to these many issues
only HDFS-8277 couldn't find a conclusion.
If this issue is something critical for you, in that case you may try your luck
on the mailing lists as well, {{common-dev}} & {{hdfs-dev}}
https://hadoop.apache.org/mailing_lists.html
> 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
