[jira] [Updated] (HDDS-8931) Allow EC PipelineChoosingPolicy to be defined separately from Ratis

["ASF GitHub Bot (Jira)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/HDDS-8931?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

ASF GitHub Bot updated HDDS-8931:
---------------------------------
    Labels: pull-request-available  (was: )

> Allow EC PipelineChoosingPolicy to be defined separately from Ratis
> -------------------------------------------------------------------
>
>                 Key: HDDS-8931
>                 URL: https://issues.apache.org/jira/browse/HDDS-8931
>             Project: Apache Ozone
>          Issue Type: Sub-task
>          Components: SCM
>            Reporter: Stephen O'Donnell
>            Assignee: Stephen O'Donnell
>            Priority: Major
>              Labels: pull-request-available
>
> Cluster may have set the PipelineChoosingPolicy to the HealthyPipelineChoosePolicy for Ratis, but it adds overhead and is not necessary for EC, as the EC pipeline is always healthy:
> {code}
>   public boolean isHealthy() {
>     // EC pipelines are not reported by the DN and do not have a leader. If a
>     // node goes stale or dead, EC pipelines will by closed like RATIS pipelines
>     // but at the current time there are not other health metrics for EC.
>     if (replicationConfig.getReplicationType() == ReplicationType.EC) {
>       return true;
>     }
>     ...
> {code}
> To allow for flexibility, add a new config for the ECPipelineChoosingPolicy so it can be different from the Ratis policy. 



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@ozone.apache.org
For additional commands, e-mail: issues-help@ozone.apache.org