You are viewing a plain text version of this content. The canonical link for it is here.
Posted to hdfs-dev@hadoop.apache.org by "Xiaoyu Yao (JIRA)" <ji...@apache.org> on 2017/05/20 17:26:04 UTC

[jira] [Created] (HDFS-11860) Ozone: SCM: SCMContainerPlacementCapacity#chooseNode chosen node is not removed from healthy list.

Xiaoyu Yao created HDFS-11860:
---------------------------------

             Summary: Ozone: SCM: SCMContainerPlacementCapacity#chooseNode chosen node is not removed from healthy list.
                 Key: HDFS-11860
                 URL: https://issues.apache.org/jira/browse/HDFS-11860
             Project: Hadoop HDFS
          Issue Type: Sub-task
          Components: ozone
    Affects Versions: HDFS-7240
            Reporter: Xiaoyu Yao
            Assignee: Xiaoyu Yao


This was caught in Jenkins run. After debugging, found the cause is the 
logic below where the node was returned without being removed from the healthy list for next round. As a result, there could be duplicated datanodes chosen with pipeline size smaller than expected. I will post a fix soon. 

{code}
SCMContainerPlacementCapacity#chooseNode
     // There is a possibility that both numbers will be same.
     // if that is so, we just return the node.
     if (firstNodeNdx == secondNodeNdx) {
      return healthyNodes.get(firstNodeNdx);
     }

{code}



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

---------------------------------------------------------------------
To unsubscribe, e-mail: hdfs-dev-unsubscribe@hadoop.apache.org
For additional commands, e-mail: hdfs-dev-help@hadoop.apache.org