You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ozone.apache.org by "Chung En Lee (Jira)" <ji...@apache.org> on 2025/10/21 20:56:01 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 ]
Chung En Lee updated HDDS-5478:
-------------------------------
Target Version/s: 2.2.0
2.2.0 (was: 2.1.0)
<<Bulk update>>
Apache Ozone 2.1.0 release is in progress. I'm updating all unresolved jiras targeting 2.1.0 to retarget 2.2.0.
> 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.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@ozone.apache.org
For additional commands, e-mail: issues-help@ozone.apache.org