[ 
https://issues.apache.org/jira/browse/HDDS-1464?focusedWorklogId=234970&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-234970
 ]

ASF GitHub Bot logged work on HDDS-1464:
----------------------------------------

                Author: ASF GitHub Bot
            Created on: 29/Apr/19 23:07
            Start Date: 29/Apr/19 23:07
    Worklog Time Spent: 10m 
      Work Description: hadoop-yetus commented on pull request #785: HDDS-1464. 
Client should have different retry policies for different exceptions.
URL: https://github.com/apache/hadoop/pull/785#discussion_r279571146
 
 

 ##########
 File path: 
hadoop-ozone/client/src/main/java/org/apache/hadoop/ozone/client/io/KeyOutputStream.java
 ##########
 @@ -500,12 +505,16 @@ private void markStreamClosed() {
     cleanup();
     closed = true;
   }
-
+  
 
 Review comment:
   whitespace:end of line
   
 
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


Issue Time Tracking
-------------------

    Worklog Id:     (was: 234970)
    Time Spent: 0.5h  (was: 20m)

> 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
>              Labels: pull-request-available
>          Time Spent: 0.5h
>  Remaining Estimate: 0h
>
> 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

Reply via email to