[
https://issues.apache.org/jira/browse/HDFS-14201?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16866839#comment-16866839
]
Hudson commented on HDFS-14201:
-------------------------------
FAILURE: Integrated in Jenkins build Hadoop-trunk-Commit #16778 (See
[https://builds.apache.org/job/Hadoop-trunk-Commit/16778/])
HDFS-14201. Ability to disallow safemode NN to become active. (inigoiri: rev
3ab77d9bc9eacfdb218b68988235a921c810b0d1)
* (edit)
hadoop-hdfs-project/hadoop-hdfs/src/main/java/org/apache/hadoop/hdfs/DFSConfigKeys.java
* (edit)
hadoop-hdfs-project/hadoop-hdfs/src/test/java/org/apache/hadoop/hdfs/server/namenode/ha/TestHASafeMode.java
* (edit)
hadoop-common-project/hadoop-common/src/main/java/org/apache/hadoop/ipc/Server.java
* (edit)
hadoop-hdfs-project/hadoop-hdfs/src/site/markdown/HDFSHighAvailabilityWithNFS.md
* (edit)
hadoop-hdfs-project/hadoop-hdfs/src/site/markdown/HDFSHighAvailabilityWithQJM.md
* (edit) hadoop-hdfs-project/hadoop-hdfs/src/main/resources/hdfs-default.xml
* (edit)
hadoop-hdfs-project/hadoop-hdfs/src/test/java/org/apache/hadoop/hdfs/server/namenode/ha/TestNNHealthCheck.java
* (edit)
hadoop-hdfs-project/hadoop-hdfs/src/main/java/org/apache/hadoop/hdfs/server/namenode/NameNode.java
> 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: 3.1.1, 2.9.2
> Reporter: Xiao Liang
> Assignee: Xiao Liang
> Priority: Major
> Fix For: 3.3.0
>
> Attachments: HDFS-14201.001.patch, HDFS-14201.002.patch,
> HDFS-14201.003.patch, HDFS-14201.004.patch, HDFS-14201.005.patch,
> HDFS-14201.006.patch, HDFS-14201.007.patch, HDFS-14201.008.patch,
> HDFS-14201.009.patch
>
>
> 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: [email protected]
For additional commands, e-mail: [email protected]
