You are viewing a plain text version of this content. The canonical link for it is here.
Posted to hdfs-dev@hadoop.apache.org by "Xiao Liang (JIRA)" <ji...@apache.org> on 2019/01/11 22:40:00 UTC
[jira] [Created] (HDFS-14201) Ability to disallow safemode NN to
become active
Xiao Liang created HDFS-14201:
---------------------------------
Summary: Ability to disallow safemode NN to become active
Key: HDFS-14201
URL: https://issues.apache.org/jira/browse/HDFS-14201
Project: Hadoop HDFS
Issue Type: Improvement
Components: auto-failover
Affects Versions: 2.9.2, 3.1.1
Reporter: Xiao Liang
Assignee: Xiao Liang
Currently with HA, Namenode in safemode can be possibly selected as active, for availability of both read and write, Namenodes not in safemode are better choices to become active though.
It can take tens of minutes for a cold started Namenode to get out of safemode, especially when there are large number of files and blocks in HDFS, that means if a Namenode in safemode become active, the cluster will be not fully functioning for quite a while, even if it can while there is some Namenode not in safemode.
The proposal here is to add an option, to allow Namenode to report itself as UNHEALTHY to ZKFC, if it's in safemode, so as to only allow fully functioning Namenode to become active, improving the general availability of the cluster.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: hdfs-dev-unsubscribe@hadoop.apache.org
For additional commands, e-mail: hdfs-dev-help@hadoop.apache.org