[
https://issues.apache.org/jira/browse/HDDS-5847?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Janus Chow updated HDDS-5847:
-----------------------------
Target Version/s: 1.5.0 (was: 1.4.0)
I am managing the 1.4.0 release and we currently have more than 500 issues
targeted for 1.4.0. I am moving the target field to 1.5.0.
If you are actively working on this jira and believe this should be targeted
for the 1.4.0 release, Please reach out to me via Apache email or Slack.
> Make OM Retry Policy configurable for different protocols
> ---------------------------------------------------------
>
> Key: HDDS-5847
> URL: https://issues.apache.org/jira/browse/HDDS-5847
> Project: Apache Ozone
> Issue Type: Improvement
> Components: OM HA
> Reporter: Hanisha Koneru
> Assignee: Hanisha Koneru
> Priority: Major
> Labels: pull-request-available
>
> -OMMetadataProtocol (introduced in HDDS-5534) is currently using the OMClient
> protocol's failoverProxyProvider - OMFailoverProxyProvider.-
> -If a bootstrap fails in StateMachine, the OM will shutdown. A retry attempt
> will result in connection failed exception and this exception would be
> propagated to the client. We should instead send the first exception which
> caused the OM to shutdown (bootstrap failure).- This situation will not occur
> after the changes in HDDS-5490.
> Also, currently we reuse the retry policy in OMFailoverProxyProvider
> formulated for OM client communication for the Inter Service Protocol and the
> OM Admin protocol (HDDS-5490). This does not take into account the retry
> policy required when a ReconfigurationInProgressException is encountered
> while bootstrapping or decommissioning an OM (please refer to [~bharat]'s
> comment
> [here|https://github.com/apache/ozone/pull/2886#issuecomment-996316512]). It
> would be good to separate out the retry policy based on the protocol.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
