[Bug] failed to start iodtb occasional.
- Dominant language
- Java
- Stars
- 6.4k
- Forks
- 1.2k
- Avg merge
- 1d 23h
- Merged PRs (30d)
- 115
Description
### Search before asking
- [X] I searched in the [issues](https://github.com/apache/iotdb/issues) and found nothing similar.
### Version
version: 1.3.0
### Describe the bug and provide the minimal reproduce step
Single machine deployment
datanode log:cannot send restart datanode reauest to Config-Node-leader after 10 retries.Please check dn_seed_config_node in iodtb-datanode.properties.
confignode log: Execute RestartDataNodeRequest TDataNodeRestartReq:return error code :400,message:The current ConfigNode is leader but not ready yet
ERROR o.a.i.c.s.t.ConfigNodeRPCServiceProcessor:258 - Thrift Error occurred during processing of message.
There is still a situation:
ConfigNode log keeps printing “handling pipe meta change ...”,Normal after deleting all files in the data folder。
There are a total of two situations where the database fails to start. Could you please take some time out of your busy schedule to answer your questions? Thank you
### What did you expect to see?
Successfully started the database
### What did you see instead?
none
### Anything else?
none
### Are you willing to submit a PR?
- [ ] I'm willing to submit a PR!
Contributor guide
Research direction
Start by reproducing the single-machine startup failure with the dn_seed_config_node setting in iodtb-datanode.properties, then inspect the ConfigNodeRPCServiceProcessor:258 log path and the reported restart requests. Done means identifying and resolving the startup failure so the database starts successfully without the repeated retry or not-ready errors.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- databases, distributed-systems
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100