Altinity / Altinity/clickhouse-operator
pod configured with ClusterScopeIndex, the operator cannot access correct port
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 2.6k
- Forks
- 574
- Avg merge
- 8d 6h
- Merged PRs (30d)
- 6
Description
When configure different ports for different pods, it seems operator try access clickhouse instance only through chPort which in the operator configuration.
For example: chi-examples/15-hostNetwork-02-simple-port-distribution.yaml
and chPort is 13000
E0414 16:56:04.655493 6 connection.go:83] connect():FAILED Ping(http://:@***:13000/). Err: dial tcp ****:13000 : connect: connection refused
E0414 16:56:04.655530 6 connection.go:170] Exec():FAILED connect(http://:@***:13000/) for SQL: CREATE DATABASE IF NOT EXISTS "default" Engine = Ordinary
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.
Research direction
Start with chi-examples/15-hostNetwork-02-simple-port-distribution.yaml and inspect connection.go at lines 83 and 170. Trace how the operator selects the ClickHouse port when pods use different ports instead of the configured chPort. Done means the operator connects to the correct pod port and the reported database-creation operation succeeds.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go, kubernetes
- Domain
- databases, infrastructure
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100