You are viewing a plain text version of this content. The canonical link for it is here.
Posted to hdfs-issues@hadoop.apache.org by "Siddharth Wagle (JIRA)" <ji...@apache.org> on 2019/04/29 19:22:00 UTC
[jira] [Assigned] (HDDS-1464) Client should have different retry
policies for different exceptions
[ https://issues.apache.org/jira/browse/HDDS-1464?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Siddharth Wagle reassigned HDDS-1464:
-------------------------------------
Assignee: Siddharth Wagle
> Client should have different retry policies for different exceptions
> --------------------------------------------------------------------
>
> Key: HDDS-1464
> URL: https://issues.apache.org/jira/browse/HDDS-1464
> Project: Hadoop Distributed Data Store
> Issue Type: Improvement
> Reporter: Hanisha Koneru
> Assignee: Siddharth Wagle
> Priority: Major
>
> Client should have different retry policies for different type of failures.
> For example, If a key write fails because of ContainerNotOpen exception, the client should wait for a specified interval before retrying. But if the key write fails because of lets say ratis leader election or request timeout, we want the client to retry immediately.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: hdfs-issues-unsubscribe@hadoop.apache.org
For additional commands, e-mail: hdfs-issues-help@hadoop.apache.org