Nicolas Fraison created HDFS-13295: -------------------------------------- Summary: Namenode doesn't leave safemode if dfs.namenode.safemode.replication.min set < dfs.namenode.replication.min Key: HDFS-13295 URL: https://issues.apache.org/jira/browse/HDFS-13295 Project: Hadoop HDFS Issue Type: Bug Components: namenode Environment: CDH 5.11 with HDFS-8716 backported.
dfs.namenode.replication.min=2 dfs.namenode.safemode.replication.min=1 Reporter: Nicolas Fraison When we set dfs.namenode.safemode.replication.min < dfs.namenode.replication.min from HDFS-8716 patch the number of replica for which it will increase the safe block count must be equal to dfs.namenode.safemode.replication.min in `FSNamesystem.incrementSafeBlockCount` When reading modification from edits, the replica number for new blocks is set at min(numNodes, dfs.namenode.replication.min) in BlockManager.completeBlock which is greater than dfs.namenode.safemode.replication.min. Due to that safe block count never reach number of available blocks and namenode doesn't leave automatically the safemode -- This message was sent by Atlassian JIRA (v7.6.3#76005) --------------------------------------------------------------------- To unsubscribe, e-mail: hdfs-dev-unsubscr...@hadoop.apache.org For additional commands, e-mail: hdfs-dev-h...@hadoop.apache.org