Altinity / Altinity/clickhouse-operator
Pod Disruption Budget per shard configuration
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 2.6k
- Forks
- 574
- Avg merge
- 8d 6h
- Merged PRs (30d)
- 6
Description
Hi there,
Currently, PDBs (Pod Disruption Budgets) are being created per cluster with a value of 1 for MAX UNAVAILABLE. This setup, especially with a large number of clusters and numerous shards, leads to prolonged reconciliation times.
One potential improvement could involve parallelizing and expediting this process by creating PDBs per shard within a cluster. In this scenario, each shard would have a 1of MAX UNAVAILABLE of replica.
Is it possible to configure the operator in such a manner?
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
The issue names no files, tests, or entry points. Review how the operator configures Pod Disruption Budgets for ClickHouse clusters, determine whether per-shard MAX UNAVAILABLE settings are supported or need a design, and define completion as a tested, documented configuration that reduces reconciliation contention.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go, kubernetes
- Domain
- databases, infrastructure
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100