When deploying 3 replicas using Helm, an error occurs when the local driver client tries to connect.
Open
@yu285 is already working on this.
Since Jul 3, 2024.
bug
- Dominant language
- C
- Stars
- 25.1k
- Forks
- 5k
- Avg merge
- 4d 59m
- Merged PRs (30d)
- 7
Description
Bug Description
When I deployed using the official Helm package and set replicaCount to 3, I could see all node statuses as normal when accessing the management page on port 6060. However, when connecting via a local client driver, it connects but shows an error message.
To Reproduce
Steps to reproduce the behavior:
- Download the official Helm 3 package.
- Change the Tdengine version to 3.3.1.0.
- After deployment, use the client driver to modify firstEp to connect to the cluster.
Expected Behavior
There should be no error.
Screenshots
Environment (please complete the following information):
- OS: official images
- TDengine Version 3.3.1.0
Additional Context
https://docs.tdengine.com/deployment/helm/
https://github.com/taosdata/TDengine-Operator/raw/3.0/helm/tdengine-3.0.2.tgz
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.
Assessment
This issue has not been assessed yet.