IoTDB Cluster Error
- Dominant language
- Java
- Stars
- 6.4k
- Forks
- 1.2k
- Avg merge
- 1d 23h
- Merged PRs (30d)
- 115
Description
Hello Team,
We are trying to run cluster using 2 servers say n1,n2(with 1C1D on each). With normal configuration the cluster is performing correctly.
Then to test data availability I stopped one of the datanode (say datanode of n2), after this when I ran some query to fetch the data,
it throws error like can't connect to datanode on n2. I tried to increase the replication factor as well, but when I changed the
replication factor to 2 then I am having this issue.
2022-08-04 02:43:40,679 [main] ERROR o.a.i.c.s.ConfigNodeCommandLine:71 - Meet error when doing start checking
org.apache.iotdb.commons.exception.ConfigurationException: Parameter data_replication_factor can not be 2, please set to: 1
at org.apache.iotdb.confignode.conf.ConfigNodeStartupCheck.checkGlobalConfig(ConfigNodeStartupCheck.java:103)
at org.apache.iotdb.confignode.conf.ConfigNodeStartupCheck.startUpCheck(ConfigNodeStartupCheck.java:65)
at org.apache.iotdb.confignode.service.ConfigNodeCommandLine.run(ConfigNodeCommandLine.java:69)
at org.apache.iotdb.commons.ServerCommandLine.doMain(ServerCommandLine.java:58)
at org.apache.iotdb.confignode.service.ConfigNode.main(ConfigNode.java:84)
Contributor guide
Research direction
Start with ConfigNodeStartupCheck.java, where the reported startup check rejects data_replication_factor=2, and review the cluster configuration involved in the n1/n2 scenario. Reproduce the query after stopping n2's datanode and verify whether the replication-factor setting permits the cluster to remain available without that datanode.
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