You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ozone.apache.org by "Hanisha Koneru (Jira)" <ji...@apache.org> on 2020/04/27 17:14:00 UTC
[jira] [Resolved] (HDDS-3465) OM Failover retry happens too quickly
when new leader suggested and retrying on same OM
[ https://issues.apache.org/jira/browse/HDDS-3465?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Hanisha Koneru resolved HDDS-3465.
----------------------------------
Resolution: Fixed
> OM Failover retry happens too quickly when new leader suggested and retrying on same OM
> ---------------------------------------------------------------------------------------
>
> Key: HDDS-3465
> URL: https://issues.apache.org/jira/browse/HDDS-3465
> Project: Hadoop Distributed Data Store
> Issue Type: Bug
> Components: HA
> Reporter: Uma Maheswara Rao G
> Assignee: Uma Maheswara Rao G
> Priority: Blocker
> Labels: pull-request-available
>
> When OM throws No leader exception with suggested leader.
> Client side failover happens too quickly.
> Incremental timeouts does not kick in this flow as we don't update lastOM/currentOM ids in this flow.
>
>
--
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