[
https://issues.apache.org/jira/browse/HDDS-2986?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ethan Rose updated HDDS-2986:
-----------------------------
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.
> MiniOzoneChaosCluster exits because of datanode shutdown
> --------------------------------------------------------
>
> Key: HDDS-2986
> URL: https://issues.apache.org/jira/browse/HDDS-2986
> Project: Apache Ozone
> Issue Type: Sub-task
> Components: Ozone Datanode
> Reporter: Mukul Kumar Singh
> Assignee: Siddharth Wagle
> Priority: Major
> Labels: MiniOzoneChaosCluster
> Attachments: HDDS-2986.test.patch
>
>
> MiniOzoneChaosCluster exits because of datanode shutdown
> {code}
> 2020-02-06 18:50:50,760 [Datanode State Machine Thread - 0] ERROR
> statemachine.DatanodeStateMachine (DatanodeStateMachine.java:start(219)) -
> DatanodeStateMachine Shutdown due to an critical error
> 2020-02-06 18:50:50,772 [RatisApplyTransactionExecutor 0] INFO
> interfaces.Container (KeyValueContainer.java:flushAndSyncDB(400)) - Container
> 30 is synced with bcsId 7490.
> 2020-02-06 18:50:50,774 [RatisApplyTransactionExecutor 0] INFO
> interfaces.Container (KeyValueContainer.java:close(338)) - Container 30 is
> closed with bcsId 7490.
> 2020-02-06 18:50:50,774 [Datanode State Machine Thread - 0] ERROR
> report.ReportManager (ReportManager.java:shutdown(82)) - Failed to shutdown
> Report Manager
> java.lang.InterruptedException
> at
> java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject.reportInterruptAfterWait(AbstractQueuedSynchronizer.java:2014)
> at
> java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject.awaitNanos(AbstractQueuedSynchronizer.java:2088)
> at
> java.util.concurrent.ThreadPoolExecutor.awaitTermination(ThreadPoolExecutor.java:1475)
> at
> org.apache.hadoop.ozone.container.common.report.ReportManager.shutdown(ReportManager.java:80)
> at
> org.apache.hadoop.ozone.container.common.statemachine.DatanodeStateMachine.stopDaemon(DatanodeStateMachine.java:411)
> at
> org.apache.hadoop.ozone.HddsDatanodeService.stop(HddsDatanodeService.java:474)
> at
> org.apache.hadoop.ozone.HddsDatanodeService.terminateDatanode(HddsDatanodeService.java:454)
> at
> org.apache.hadoop.ozone.container.common.statemachine.DatanodeStateMachine.start(DatanodeStateMachine.java:220)
> at
> org.apache.hadoop.ozone.container.common.statemachine.DatanodeStateMachine.lambda$startDaemon$0(DatanodeStateMachine.java:365)
> at java.lang.Thread.run(Thread.java:748)
> 2020-02-06 18:50:50,774 [Datanode State Machine Thread - 0] ERROR
> statemachine.DatanodeStateMachine (DatanodeStateMachine.java:close(272)) -
> Error attempting to shutdown.
> java.lang.InterruptedException
> at
> java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject.awaitNanos(AbstractQueuedSynchronizer.java:2067)
> at
> java.util.concurrent.ThreadPoolExecutor.awaitTermination(ThreadPoolExecutor.java:1475)
> at
> org.apache.hadoop.ozone.container.common.statemachine.DatanodeStateMachine.close(DatanodeStateMachine.java:264)
> at
> org.apache.hadoop.ozone.container.common.statemachine.DatanodeStateMachine.stopDaemon(DatanodeStateMachine.java:412)
> at
> org.apache.hadoop.ozone.HddsDatanodeService.stop(HddsDatanodeService.java:474)
> at
> org.apache.hadoop.ozone.HddsDatanodeService.terminateDatanode(HddsDatanodeService.java:454)
> at
> org.apache.hadoop.ozone.container.common.statemachine.DatanodeStateMachine.start(DatanodeStateMachine.java:220)
> at
> org.apache.hadoop.ozone.container.common.statemachine.DatanodeStateMachine.lambda$startDaemon$0(DatanodeStateMachine.java:365)
> at java.lang.Thread.run(Thread.java:748)
> {code}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
