Sihan Liu
Reputation: 395
How to prevent the 39352 process stuck and log continue to print for process executing worker of Apache IoTDB?
I got confignode tendpoint error and I know it should be something wrong with my confignode execution in Apache IoTDB. I checked the log information and find that pid 39252 work process seems to be stuck, and this message [ProcExecWorker-8 AbstractNodeProcedure: 39 - procedureld 39352 causing the subsequent log to continue to print. This may be the reason why my confignode went down. Anyone know why this procedure may be stuck?
Upvotes: 0
Views: 11
Answers (1)
Monster Zhang
Reputation: 152
The new version, 1.3.0 of Apache IoTDB has already fixed this problem. Therefore, you can upgrade your using version and see if this problem has been solved.
Upvotes: 0
Related Questions
- How to add a fixed column to the data returned from `select avg` query in Apache IoTDB?
- How to fix the gap between logs when restarting ConfigNode in Apache IoTDB?
- When reported current confignode is not ready and all query progress got timeout, what configuration should be checked in Apache IoTDB?
- For a two-stage cluster deployed in Apache IoTDB, why the confignode of the second server cannot be started and added to the seed confignode?
- Why did the cluster cannot be still running when one ConfigNode and DataNode went down in Apache IoTDB?
- For new nodes, how can the cn_target_config_node_list parameter be set in Apache IoTDB?
- How to start the first ConfigNode of Apache IoTDB cluster version after clearing data?
- How to kill a stuck query process in Apache IoTDB when time series data is large?