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:37:12 UTC
[jira] [Updated] (HDDS-2730) Datanode shutdown should be more
informative when error occurs
[ https://issues.apache.org/jira/browse/HDDS-2730?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Ethan Rose updated HDDS-2730:
-----------------------------
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.
> Datanode shutdown should be more informative when error occurs
> ---------------------------------------------------------------
>
> Key: HDDS-2730
> URL: https://issues.apache.org/jira/browse/HDDS-2730
> Project: Apache Ozone
> Issue Type: Bug
> Reporter: Shashikant Banerjee
> Priority: Major
>
> When datanode shuts down , the following logging seems insufficinet as to why shhutdown is taking place:
> {code:java}
> 2019-12-13 03:11:16,404 ERROR org.apache.hadoop.ozone.container.common.statemachine.StateContext: Critical error occurred in StateMachine, setting shutDownMachine
> 2019-12-13 03:11:18,096 ERROR org.apache.hadoop.ozone.container.common.statemachine.DatanodeStateMachine: DatanodeStateMachine Shutdown due to an critical error
> {code}
> This can be made more informative
--
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