[
https://issues.apache.org/jira/browse/HDFS-8391?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14937132#comment-14937132
]
Hudson commented on HDFS-8391:
------------------------------
FAILURE: Integrated in Hadoop-Hdfs-trunk #2379 (See
[https://builds.apache.org/job/Hadoop-Hdfs-trunk/2379/])
HDFS-8391. NN should consider current EC tasks handling count from DN
(zhezhang: rev c99c3379282779e11ebda88d845bb89407f2f350)
* hadoop-hdfs-project/hadoop-hdfs/CHANGES-HDFS-EC-7285.txt
*
hadoop-hdfs-project/hadoop-hdfs/src/main/java/org/apache/hadoop/hdfs/server/datanode/DataNode.java
*
hadoop-hdfs-project/hadoop-hdfs/src/main/java/org/apache/hadoop/hdfs/server/datanode/erasurecode/ErasureCodingWorker.java
> NN should consider current EC tasks handling count from DN while assigning
> new tasks
> ------------------------------------------------------------------------------------
>
> Key: HDFS-8391
> URL: https://issues.apache.org/jira/browse/HDFS-8391
> Project: Hadoop HDFS
> Issue Type: Sub-task
> Components: datanode, namenode
> Reporter: Uma Maheswara Rao G
> Assignee: Uma Maheswara Rao G
> Fix For: HDFS-7285
>
> Attachments: HDFS-8391-01.patch
>
>
> Currently NN will pick the (maxStreams-XmitsCount) number of ECtasks at a
> time for assigning to the respective DN.
> {code}
> //get datanode commands
> final int maxTransfer = blockManager.getMaxReplicationStreams()
> - xmitsInProgress;
> {code}
> But right now we increment xmitsInProgress count at DN only for regular
> replication tasks but not for ECWorker tasks.
> So, either we should treat this logic separately for EC or we should consider
> EC current task handling count form DN.
> This jira for discussing more for this case.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
