You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ozone.apache.org by "Ethan Rose (Jira)" <ji...@apache.org> on 2021/10/20 20:40:08 UTC

[jira] [Updated] (HDDS-5478) Improve error logging in OMStateMachine

     [ https://issues.apache.org/jira/browse/HDDS-5478?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Ethan Rose updated HDDS-5478:
-----------------------------
    Target Version/s: 1.3.0  (was: 1.2.0)

I am managing the 1.2.0 release and we currently have more than 600 issues targeted for 1.2.0. I am moving the target field to 1.3.0.

If you are actively working on this jira and believe this should be targeted for the 1.2.0 release, Please reach out to me via Apache email or Slack.

> Improve error logging in OMStateMachine
> ---------------------------------------
>
>                 Key: HDDS-5478
>                 URL: https://issues.apache.org/jira/browse/HDDS-5478
>             Project: Apache Ozone
>          Issue Type: Improvement
>          Components: OM
>            Reporter: Hanisha Koneru
>            Assignee: Hanisha Koneru
>            Priority: Major
>
> If some exception occurs in a StateMachine implemented method, the exception is propagated back to Ratis and then through Ratis back again to StateMachine. In this back and forth, the exception could be lost. 
> While working on OM Bootstrap, I encountered a NullPointer exception in OMStateMachine which cause Ratis (and eventually StateMachine) to shutdown with a "client cancelled" exception. It would have helped in debugging if the OMStateMachine had logged the initial exception. 



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@ozone.apache.org
For additional commands, e-mail: issues-help@ozone.apache.org