[
https://issues.apache.org/jira/browse/HDDS-2032?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Shashikant Banerjee updated HDDS-2032:
--------------------------------------
Description: 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. (was:
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 right. 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.)
> 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
> Fix For: 0.5.0
>
>
> 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]
