[
https://issues.apache.org/jira/browse/HDDS-1464?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16829643#comment-16829643
]
Siddharth Wagle commented on HDDS-1464:
---------------------------------------
Thanks [~hanishakoneru] for filing this, I will take this up.
> 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-unsubscr...@hadoop.apache.org
For additional commands, e-mail: hdfs-issues-h...@hadoop.apache.org
