Altinity / Altinity/clickhouse-operator
Annotation for current CHK quorum leader
Open
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 2.6k
- Forks
- 574
- Avg merge
- 8d 6h
- Merged PRs (30d)
- 6
Description
Operator will track and add annotation for current CHK quorum leader.
For huge clusters, heavy loaded keepers, it can make sense to shield leader from client requests, only manage intra quorum traffic.
Having such annotation allow to exclude such node from client facing service.
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
No files or tests are named. Start by tracing how the operator identifies the current ClickHouse Keeper quorum leader and configures client-facing services. Done means the current leader can be marked with an annotation and excluded from client-facing service endpoints while remaining available for quorum traffic.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go, kubernetes
- Domain
- databases, infrastructure
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 48/100