[HDDS-2206] Separate handling for OMException and IOException in the Ozone Manager

• Type: Sub-task
• Status: Reopened
• Priority: Major
• Resolution: Unresolved
• Component/s: Ozone Manager
• Target Version/s: 0.5.0
• Assignee: Unassigned
• Reporter: Supratim Deka
• Created: 30/Sep/19 09:35
• Updated: 22/Nov/19 05:15

Description

As part of improving error propagation from the OM for ease of troubleshooting and diagnosis, the proposal is to handle IOExceptions separately from the business exceptions which are thrown as OMExceptions.
Handling for OMExceptions will not be changed in this jira.
Handling for IOExceptions will include logging the stacktrace on the server, and propagation to the client under the control of a config parameter.

Similar handling is also proposed for SCMException.

Issue Links

• links to: GitHub Pull Request #12
• links to: GitHub Pull Request #1637