You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ozone.apache.org by "Ethan Rose (Jira)" <ji...@apache.org> on 2021/10/20 20:39:10 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 ]
Ethan Rose updated HDDS-3138:
-----------------------------
Target Version/s: 1.3.0 (was: 1.2.0)
I am managing the 1.2.0 release and we currently have more than 600 issues targeted for 1.2.0. I am moving the target field to 1.3.0.
If you are actively working on this jira and believe this should be targeted for the 1.2.0 release, Please reach out to me via Apache email or Slack.
> Fix pipeline datanode limit on cluster with rack awareness
> ----------------------------------------------------------
>
> Key: HDDS-3138
> URL: https://issues.apache.org/jira/browse/HDDS-3138
> Project: Apache Ozone
> 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: issues-unsubscribe@ozone.apache.org
For additional commands, e-mail: issues-help@ozone.apache.org