[
https://issues.apache.org/jira/browse/HDDS-8698?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Attila Doroszlai resolved HDDS-8698.
------------------------------------
Fix Version/s: 1.4.0
Resolution: Implemented
> EC: Avoid unbounded pipeline creation if all existing pipelines don't meet
> criteria
> -----------------------------------------------------------------------------------
>
> Key: HDDS-8698
> URL: https://issues.apache.org/jira/browse/HDDS-8698
> Project: Apache Ozone
> Issue Type: Sub-task
> Reporter: Stephen O'Donnell
> Assignee: Stephen O'Donnell
> Priority: Major
> Labels: pull-request-available
> Fix For: 1.4.0
>
>
> Currently, if the pipeline limit is not reached, when a new block is
> requested, a new pipeline is allocated and returned to the client.
> If the pipeline limit is reached, we attempt to return a pipeline from the
> existing set.
> If none of those pipelines meet the criteria, then we fall back to creating
> another pipeline. This could result in unbounded pipeline growth if a client
> is having problems.
> We should therefore limit the pipelines that can be created via this
> exceptional case.
> For example, if we close some pipelines when searching the existing list (due
> to them being full), we know we have freed up some capacity to create a new
> pipeline.
> Also, or alternative, we could allow the limit to be exceeded by some
> controlled factor - eg 10% and if the limit is beyond that, return a failure
> to the client.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
