You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ozone.apache.org by "Arpit Agarwal (Jira)" <ji...@apache.org> on 2020/06/01 21:33:00 UTC
[jira] [Updated] (HDDS-3138) Fix pipeline datanode limit on cluster
with rack awareness
[ https://issues.apache.org/jira/browse/HDDS-3138?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Arpit Agarwal updated HDDS-3138:
--------------------------------
Fix Version/s: (was: 0.6.0)
Target Version/s: 0.6.0
Labels: TriagePending (was: )
> Fix pipeline datanode limit on cluster with rack awareness
> ----------------------------------------------------------
>
> Key: HDDS-3138
> URL: https://issues.apache.org/jira/browse/HDDS-3138
> Project: Hadoop Distributed Data Store
> Issue Type: Bug
> Components: SCM
> Reporter: Li Cheng
> Assignee: Simon Su
> Priority: Major
> Labels: TriagePending
>
> Deployed on cluster with 8 datanodes and rack awareness enabled. (2/3/3). Pipeline limit on datanode is 5.
>
> turned out there are pipeline which can have over 5.
>
> Perhaps should not count out CLOSE pipeline when filter the limit.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: ozone-issues-unsubscribe@hadoop.apache.org
For additional commands, e-mail: ozone-issues-help@hadoop.apache.org