[
https://issues.apache.org/jira/browse/HADOOP-4910?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12662056#action_12662056
]
Hairong Kuang commented on HADOOP-4910:
---------------------------------------
Ant test-patch passed
[exec] +1 overall.
[exec]
[exec] +1 @author. The patch does not contain any @author tags.
[exec]
[exec] +1 tests included. The patch appears to include 9 new or
modified tests.
[exec]
[exec] +1 javadoc. The javadoc tool did not generate any warning
messages.
[exec]
[exec] +1 javac. The applied patch does not increase the total number
of javac compiler warnings.
[exec]
[exec] +1 findbugs. The patch does not introduce any new Findbugs
warnings.
[exec]
[exec] +1 Eclipse classpath. The patch retains Eclipse classpath
integrity.
[exec]
Ant test-core failed with a known junit test failure reported at HADOOP-4907.
All other unit tests passed.
> NameNode should exclude corrupt replicas when choosing excessive replicas to
> delete
> -----------------------------------------------------------------------------------
>
> Key: HADOOP-4910
> URL: https://issues.apache.org/jira/browse/HADOOP-4910
> Project: Hadoop Core
> Issue Type: Bug
> Components: dfs
> Affects Versions: 0.17.0
> Reporter: Hairong Kuang
> Assignee: Hairong Kuang
> Priority: Blocker
> Fix For: 0.18.3
>
> Attachments: overReplicated.patch, overReplicated1.patch,
> overReplicated2-br18.patch, overReplicated2.patch
>
>
> Currently, when NameNode handles an over-replicated block in
> FSNamesystem#processOverReplicatedBlock, it excludes ones already in
> excessReplicateMap and decommissed ones, but it treats a corrupt replica as a
> valid one. This may lead to unnecessary deletion of more replicas and thus
> cause data lose. It should exclude corrupt replicas as well.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
