[HDDS-2032] Ozone client should retry writes in case of any ratis/stateMachine exceptions

• Type: Bug
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 0.5.0
• Fix Version/s: 0.5.0
• Component/s: Ozone Client
• Labels: pull-request-available
• Target Version/s: 0.5.0
• Assignee: Shashikant Banerjee
• Reporter: Shashikant Banerjee
• Created: 26/Aug/19 05:34
• Updated: 24/Feb/20 20:53
• Resolved: 18/Sep/19 17:01

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.

Issue Links

• links to: GitHub Pull Request #1420