You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ozone.apache.org by "Shashikant Banerjee (Jira)" <ji...@apache.org> on 2021/01/21 10:42:00 UTC
[jira] [Assigned] (HDDS-4710) Pipeline: chooseDatanodes function
random pick not working
[ https://issues.apache.org/jira/browse/HDDS-4710?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Shashikant Banerjee reassigned HDDS-4710:
-----------------------------------------
Assignee: Xu Shao Hong
> Pipeline: chooseDatanodes function random pick not working
> -----------------------------------------------------------
>
> Key: HDDS-4710
> URL: https://issues.apache.org/jira/browse/HDDS-4710
> Project: Hadoop Distributed Data Store
> Issue Type: Bug
> Reporter: Xu Shao Hong
> Assignee: Xu Shao Hong
> Priority: Major
> Labels: pull-request-available
> Fix For: 1.1.0
>
> Attachments: image-2021-01-15-17-46-31-492.png
>
>
> I was trying to configure a four-node cluster to test SCM HA, after configuring the ozone.datanode.pipeline.limit to 3 and 5 separately, the pipeline existed only chose the first three data nodes, the fourth node was never chosen.(They are equal nodes)
> The bug here is due to that the method *{color:#172b4d}+chooseDatanodes+{color}* in PipelinePlacementPolicy calls *+super.getResultSet+*, in which another method +{color:#172b4d}*chooseNode*{color}+ is called. This +*chooseNode*+ method is an abstract method in the superclass and is overridden in PipelinePlacementPolicy. The overridden version uses a simple logic instead of a randomly chosen policy which incurs my problem.
>
>
> * !image-2021-01-15-17-46-31-492.png!
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@ozone.apache.org
For additional commands, e-mail: issues-help@ozone.apache.org