[
https://issues.apache.org/jira/browse/HADOOP-3685?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12611379#action_12611379
]
Hadoop QA commented on HADOOP-3685:
-----------------------------------
-1 overall. Here are the results of testing the latest attachment
http://issues.apache.org/jira/secure/attachment/12385220/rereplicationPolicy.patch
against trunk revision 674645.
+1 @author. The patch does not contain any @author tags.
+1 tests included. The patch appears to include 3 new or modified tests.
-1 patch. The patch command could not apply the patch.
Console output:
http://hudson.zones.apache.org/hudson/job/Hadoop-Patch/2804/console
This message is automatically generated.
> Unbalanced replication target
> ------------------------------
>
> Key: HADOOP-3685
> URL: https://issues.apache.org/jira/browse/HADOOP-3685
> Project: Hadoop Core
> Issue Type: Bug
> Components: dfs
> Affects Versions: 0.17.0
> Reporter: Koji Noguchi
> Assignee: Hairong Kuang
> Priority: Blocker
> Fix For: 0.17.2, 0.18.0
>
> Attachments: rereplicationPolicy.patch
>
>
> In HADOOP-3633, namenode was assigning some datanodes to receive hundreds of
> blocks in a short period which caused datanodes to go out of memroy(threads).
> Most of them were from remote rack.
> Looking at the code,
> {noformat}
> 166 chooseLocalRack(results.get(1), excludedNodes, blocksize,
> 167 maxNodesPerRack, results);
> {noformat}
> was sometimes not choosing the local rack of the writer(source).
> As a result, when a datanode goes down, other datanodes on the same rack were
> getting large number of blocks from remote racks.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
