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

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

                Author: ASF GitHub Bot
            Created on: 17/Sep/19 15:40
            Start Date: 17/Sep/19 15:40
    Worklog Time Spent: 10m 
      Work Description: mukul1987 commented on issue #1420: HDDS-2032. Ozone 
client should retry writes in case of any ratis/stateMachine exceptions.
URL: https://github.com/apache/hadoop/pull/1420#issuecomment-532278299
 
 
   Thanks for working on this @bshashikant , there are some conflicts with this 
patch. Can you please rebase.
 
----------------------------------------------------------------
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:
[email protected]


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

    Worklog Id:     (was: 313754)
    Time Spent: 1h  (was: 50m)

> Ozone client should retry writes in case of any ratis/stateMachine exceptions
> -----------------------------------------------------------------------------
>
>                 Key: HDDS-2032
>                 URL: https://issues.apache.org/jira/browse/HDDS-2032
>             Project: Hadoop Distributed Data Store
>          Issue Type: Bug
>          Components: Ozone Client
>    Affects Versions: 0.5.0
>            Reporter: Shashikant Banerjee
>            Assignee: Shashikant Banerjee
>            Priority: Major
>              Labels: pull-request-available
>             Fix For: 0.5.0
>
>          Time Spent: 1h
>  Remaining Estimate: 0h
>
> Currently, Ozone client retry writes on a different pipeline or container in 
> case of some specific exceptions. But in case, it sees exception such as 
> DISK_FULL, CONTAINER_UNHEALTHY or any corruption , it just aborts the write. 
> In general, the every such exception on the client should be a retriable  
> exception in ozone client and on some specific exceptions, it should take 
> some more specific exception like excluding certain containers or pipelines 
> while retrying or informing SCM of a corrupt replica etc.



--
This message was sent by Atlassian Jira
(v8.3.2#803003)

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to