[Bug] 执行start-all.sh后无法启动集群问题
Nobody has claimed this yet.
Assessment
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Newbie friendliness
- 78/100
- Issue type
- Bug
- Clarity
- Clearly specified
- Activity status
- Quiet
- Tech stack
- bash, java
- Domain
- distributed-systems
Research direction
Start with sbin/cluster/start-all.sh and reproduce the issue on the documented 3C3D cluster setup, focusing on the remote bash invocation and how it receives the Java environment. Confirm the script can find Java over SSH and that the ConfigNodes and DataNodes actually start successfully.
Written by the indexing model from the issue text.
Description
Search before asking
- I searched in the issues and found nothing similar.
Version
2.0.10，3C3D集群
Describe the bug and provide the minimal reproduce step
发现start-all.sh没办法启动集群，排查是ssh到目标主机后找不到java环境变量。我已确认配置了环境变量，在/etc/profile,/etc/bashrc,~/.bashrc,~/.profile都加上了环境变量，都执行了source xxx，服务器也尝试重启还是提示找不到java。使用ssh测试结果如下：
最后通过在start-all.sh文件中的bash命令后加上-lc解决了该问题，希望能在官方脚本上加上。
What did you expect to see?
正常启动集群
What did you see instead?
root@n1:/opt/iotdb# ./sbin/cluster/start-all.sh
The system starts the ConfigNode And DataNode of n1
The system starts the ConfigNode And DataNode of n2
The system starts the ConfigNode And DataNode of n3
Cluster startup complete ...
实际上没启动
Anything else?
No response
Are you willing to submit a PR?
- I'm willing to submit a PR!
- Dominant language
- Java
- Stars
- 6.4k
- Forks
- 1.2k
- Avg merge
- 1d 8h
- Merged PRs (30d)
- 129
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from apache/iotdb
-
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
-
IoTDB Edge: stop-edge.sh does not stop its own process when IOTDB_HOME is set, and reports success Open
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
-
[Bug] findColumn throws NullPointerException instead of SQLException for an unknown column name Open
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
infinispan/infinispan#18150 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
-
untriaged
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
opensearch-project/k-NN#3597 ·
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 82/100