[
https://issues.apache.org/jira/browse/HDFS-8716?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14735460#comment-14735460
]
Hadoop QA commented on HDFS-8716:
---------------------------------
\\
\\
| (x) *{color:red}-1 overall{color}* |
\\
\\
|| Vote || Subsystem || Runtime || Comment ||
| {color:red}-1{color} | patch | 0m 0s | The patch command could not apply
the patch during dryrun. |
\\
\\
|| Subsystem || Report/Notes ||
| Patch URL |
http://issues.apache.org/jira/secure/attachment/12745376/HDFS-8716.7.patch |
| Optional Tests | javadoc javac unit findbugs checkstyle |
| git revision | trunk / 970daaa |
| Console output |
https://builds.apache.org/job/PreCommit-HDFS-Build/12344/console |
This message was automatically generated.
> introduce a new config specifically for safe mode block count
> -------------------------------------------------------------
>
> Key: HDFS-8716
> URL: https://issues.apache.org/jira/browse/HDFS-8716
> Project: Hadoop HDFS
> Issue Type: Bug
> Reporter: Chang Li
> Assignee: Chang Li
> Attachments: HDFS-8716.1.patch, HDFS-8716.2.patch, HDFS-8716.3.patch,
> HDFS-8716.4.patch, HDFS-8716.5.patch, HDFS-8716.6.patch, HDFS-8716.7.patch,
> HDFS-8716.7.patch
>
>
> During the start up, namenode waits for n replicas of each block to be
> reported by datanodes before exiting the safe mode. Currently n is tied to
> the min replicas config. We could set min replicas to more than one but we
> might want to exit safe mode as soon as each block has one replica reported.
> This can be worked out by introducing a new config variable for safe mode
> block count
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
