[
https://issues.apache.org/jira/browse/HDFS-17763?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17940073#comment-17940073
]
ASF GitHub Bot commented on HDFS-17763:
---------------------------------------
aswinmprabhu commented on PR #7321:
URL: https://github.com/apache/hadoop/pull/7321#issuecomment-2769409476
@adityarverma - You don't need a separate ticket / new commit msg to
backport an existing commit. It should retain the same metadata of the original
commit.
> backport HDFS-16547 to hadoop 3.3 feature to block observer transition if
> namenode is in safemode
> -------------------------------------------------------------------------------------------------
>
> Key: HDFS-17763
> URL: https://issues.apache.org/jira/browse/HDFS-17763
> Project: Hadoop HDFS
> Issue Type: Improvement
> Components: namenode
> Reporter: Aditya Raj Verma
> Priority: Major
> Labels: pull-request-available
>
> Backport HDFS-16547 to hadoop 3.3 feature to dissallow observer transition if
> namenode is in safemode.
> Currently, when a Namenode is in safemode(under starting or enter safemode
> manually), we can transfer this Namenode to Observer by command. This
> Observer node may receive many requests and then throw a SafemodeException,
> this causes unnecessary failover on the client.
> So Namenode in safe mode should not be transfered to observer state.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: hdfs-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: hdfs-issues-h...@hadoop.apache.org
