apache / apache/iotdb

突然停电后,iotdb重启失败

Open
#12,453 2 comments 0 reactions 0 assignees View on GitHub
Dominant language
Java
Stars
6.4k
Forks
1.2k
Avg merge
1d 23h
Merged PRs (30d)
115

Description

使用iotdb版本号:1.2.2 服务器版本:Linux lyc-uos 4.19.0-91.82.152.uelc20.x86_64 #1 SMP Fri May 12 22:38:01 CST 2023 x86_64 x86_64 x86_64 GNU/Linux
突然停电后来电,其他mysql、redis正常开机启动,iotdb无法正常开机启动,iotdb已配置开机自启,后来手动执行启动脚本start-standalone.sh还是失败,部分日志如下:2024-04-30 13:06:11,854 [pool-37-IoTDB-ClientRPC-Processor-1] ERROR o.a.i.d.a.ClusterAuthorityFetcher:210 - Failed to connect to config node.
2024-04-30 13:06:13,165 [IoTDB-Shutdown-Hook] ERROR o.a.i.d.s.IoTDBShutdownHook:124 - Failed to report shutdown
org.apache.thrift.TException: Error in calling method reportDataNodeShutdown, because: Fail to connect to any config node. Please check status of ConfigNodes or logs of connected DataNode
at org.apache.iotdb.commons.client.sync.SyncThriftClientWithErrorHandler.intercept(SyncThriftClientWithErrorHandler.java:57)
at org.apache.iotdb.db.protocol.client.ConfigNodeClient$$EnhancerByCGLIB$$713d1e1e.reportDataNodeShutdown()
at org.apache.iotdb.db.service.IoTDBShutdownHook.run(IoTDBShutdownHook.java:119)
Caused by: org.apache.thrift.TException: Fail to connect to any config node. Please check status of ConfigNodes or logs of connected DataNode
at org.apache.iotdb.db.protocol.client.ConfigNodeClient.tryToConnect(ConfigNodeClient.java:268)
at org.apache.iotdb.db.protocol.client.ConfigNodeClient.waitAndReconnect(ConfigNodeClient.java:237)
at org.apache.iotdb.db.protocol.client.ConfigNodeClient.executeRemoteCallWithRetry(ConfigNodeClient.java:345)
at org.apache.iotdb.db.protocol.client.ConfigNodeClient.reportDataNodeShutdown(ConfigNodeClient.java:406)
at org.apache.iotdb.db.protocol.client.ConfigNodeClient$$EnhancerByCGLIB$$713d1e1e.CGLIB$reportDataNodeShutdown$6()
at org.apache.iotdb.db.protocol.client.ConfigNodeClient$$EnhancerByCGLIB$$713d1e1e$$FastClassByCGLIB$$600dc9c5.invoke()
at net.sf.cglib.proxy.MethodProxy.invokeSuper(MethodProxy.java:228)
at org.apache.iotdb.commons.client.sync.SyncThriftClientWithErrorHandler.intercept(SyncThriftClientWithErrorHandler.java:53)
... 2 common frames omitted
2024-04-30 13:06:13,165 [IoTDB-Shutdown-Hook] ERROR o.a.i.d.s.IoTDBShutdownHook:127 - Reporting DataNode shutdown failed. The cluster will still take the current DataNode as Running for a few seconds.
[iotdb-log.zip](https://github.com/apache/iotdb/files/15158550/iotdb-log.zip)

Contributor guide

Open the contributing guide

Research direction

Start with the attached iotdb-log.zip and the failure from start-standalone.sh, focusing on ConfigNode connection errors in ConfigNodeClient and ClusterAuthorityFetcher. Trace the startup path and compare the reported shutdown-hook errors with the ConfigNode status; done means the configured startup completes successfully after a power interruption.

Written by the indexing model from the issue text.

Assessment

Tech stack
java, linux
Domain
databases
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.