[
https://issues.apache.org/jira/browse/HDDS-11768?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ivan Andika resolved HDDS-11768.
--------------------------------
Fix Version/s: 2.0.0
Resolution: Implemented
> Extract SCM failover proxy provider logic
> -----------------------------------------
>
> Key: HDDS-11768
> URL: https://issues.apache.org/jira/browse/HDDS-11768
> Project: Apache Ozone
> Issue Type: Sub-task
> Components: SCM Client
> Reporter: Ivan Andika
> Assignee: Ivan Andika
> Priority: Major
> Labels: pull-request-available
> Fix For: 2.0.0
>
>
> There are a lot of duplicated SCM proxy provider logic in
> * SCMBlockLocationFailoverProxyProvider
> * SCMContainerLocationFailoverProxyProvider
> * SCMSecurityProtocolFailoverProxyProvider
> * SecretKeyProtocolFailoverProxyProvider
> It's better to extract the logic to a separate class (e.g parent class) to
> prevent divergent implementation of this critical logic.
> SingleSecretKeyProtocolProxyProvider is a proxy provider that just
> communicates with a single SCM, therefore it requires a special handling by
> exposing the getCurrentProxySCMNodeId().
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
