Altinity / Altinity/clickhouse-operator
Keeper log directory misconfiguration
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 2.6k
- Forks
- 574
- Avg merge
- 8d 6h
- Merged PRs (30d)
- 6
Description
Keeper cannot start when using operator version 0.24.4 and containers with readonly filesystem due to incorrect log directory.
Keeper log directory is hardcoded to /var/log/clickhouse-keeper-log in the:
Clickhouse-keeper however by default uses /var/log/clickhouse-keeper directory.
Edit:
Added clarifications
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 in pkg/model/chk/config/const.go at the referenced line and compare the configured Keeper log directory with the directory used by ClickHouse Keeper by default. Update the configuration so Keeper can start with a read-only filesystem, then verify the resulting directory behavior for operator version 0.24.4.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go, kubernetes
- Domain
- infrastructure
- Issue type
- Bug
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Clearly specified
- Newbie friendliness
- 55/100