[HDDS-2175] Propagate System Exceptions from the OzoneManager

• Type: Improvement
• Status: Open
• Priority: Minor
• Resolution: Unresolved
• Component/s: Ozone Manager
• Labels: Triaged
• Target Version/s: 1.5.0
• Assignee: Unassigned
• Reporter: Supratim Deka
• Created: 25/Sep/19 05:55
• Updated: 16/Dec/23 23:43

Description

Exceptions encountered while processing requests on the OM are categorized as business exceptions and system exceptions. All of the business exceptions are captured as OMException and have an associated status code which is returned to the client. The handling of these is not going to be changed.

Currently system exceptions are returned as INTERNAL ERROR to the client with a 1 line message string from the exception. The scope of this jira is to capture system exceptions and propagate the related information(including the complete stack trace) back to the client.

There are 3 sub-tasks required to achieve this
1. Separate capture and handling for OMException and the other exceptions(IOException). For system exceptions, use Hadoop IPC ServiceException mechanism to send the stack trace to the client.
2. track and propagate exceptions inside Ratis OzoneManagerStateMachine and propagate up to the OzoneManager layer (on the leader). Currently, these exceptions are not being tracked.
3. Handle and propagate exceptions from Ratis.

Will raise jira for each sub-task.

Sub-Tasks

• Separate handling for OMException and IOException in the Ozone Manager: Reopened
• Propagate System Exceptions from OM transaction apply phase: Resolved