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 2020/10/07 11:48:00 UTC
[jira] [Resolved] (HDDS-4072) Pipeline creation on a datanodes
should account for raft log disks reported
[ https://issues.apache.org/jira/browse/HDDS-4072?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Shashikant Banerjee resolved HDDS-4072.
---------------------------------------
Fix Version/s: 1.1.0
Resolution: Fixed
> Pipeline creation on a datanodes should account for raft log disks reported
> ---------------------------------------------------------------------------
>
> Key: HDDS-4072
> URL: https://issues.apache.org/jira/browse/HDDS-4072
> Project: Hadoop Distributed Data Store
> Issue Type: Sub-task
> Components: Ozone Datanode, SCM
> Reporter: Shashikant Banerjee
> Assignee: Shashikant Banerjee
> Priority: Major
> Fix For: 1.1.0
>
>
> Currently, how many pipelines a datanode will be a part is controlled by a config ozone.datanode.pipeline.limit. Now, with the no of raft log disks reported by datanode to SCM, we can potentially set the limit on pipeline capacity based on raft log disks reported instead .
--
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