Operator should add graceful shutdown to the pods
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 48/100
- Issue type
- Feature
- Clarity
- Mostly clear
- Activity status
- Quiet
- Tech stack
- go, kubernetes
- Domain
- databases, devops, infrastructure
Research direction
Start by tracing how the operator currently shuts down ClickHouse pods. Compare that flow with the issue's SYSTEM STOP MERGES, SYSTEM STOP FETCHES, in-flight checks through system.merges and system.replicated_fetches, and final SYSTEM SHUTDOWN sequence. Done means upgrades no longer kill active merges or replication fetches during shutdown.
Written by the indexing model from the issue text.
Description
The ideal graceful flow would be:
- SYSTEM STOP MERGES -- no NEW merges start
- SYSTEM STOP FETCHES -- no NEW fetches (replication) start
- Wait for in-flight merges/fetches to finish
(query system.merges / system.replicated_fetches to check) - SYSTEM SHUTDOWN -- now safe to kill, nothing in progress
What the operator does today:
- SYSTEM SHUTDOWN -- everything in progress gets killed
Upgrades can cause some race condition with various setups.
- Dominant language
- Go
- Stars
- 2.6k
- Forks
- 579
- Avg merge
- 21h 2m
- Merged PRs (30d)
- 4
Getting set up
- Ships a Dockerfile or Docker Compose file
- Has a pull request template
- Read the contributing 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.
More from Altinity/clickhouse-operator
-
Counter metrics are missing the conventional _total suffixPossibly taken A pull request linked to this issue is open or already merged. Open
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
Altinity/clickhouse-operator#2093 · 1 comment ·
Maintainers usually reply within 1 day
-
Difficulty 5/5 Over a week Newbie friendliness 18/100
Altinity/clickhouse-operator#2105 ·
Maintainers usually reply within 1 day
-
Difficulty 4/5 3-5 days Newbie friendliness 35/100
Altinity/clickhouse-operator#2098 ·
Maintainers usually reply within 1 day
-
Difficulty 4/5 3-5 days Newbie friendliness 35/100
Altinity/clickhouse-operator#2096 ·
Maintainers usually reply within 1 day
-
CHI reconcile aborts (and is never retried) when the API server briefly rejects owner-referenced objects right after the CRD is created (OpenShift OwnerReferencesPermissionEnforcement)Possibly taken A pull request linked to this issue is open or already merged. Open
Difficulty 3/5 1-2 days Newbie friendliness 72/100
Altinity/clickhouse-operator#2094 ·
Maintainers usually reply within 1 day
All issues in Altinity/clickhouse-operator
Similar issues
-
mutation: parseInt64 accepts integers that overflow int64 and wrap to a non-negative valuePossibly taken @ogulcanaydogan claimed this today. Open
Difficulty 2/5 1-3 hours Newbie friendliness 85/100
open-policy-agent/gatekeeper#4872 ·
Maintainers usually reply within 1 day
-
needs-triage
Difficulty 1/5 Under an hour Newbie friendliness 88/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
containers/kubernetes-mcp-server#1496 · 1 comment ·
Maintainers usually reply within 2 days
-
bug performance scalability
Difficulty 2/5 1-3 hours Newbie friendliness 62/100
Davidjustice28/basildb#35 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
rhysd/actionlint#761 ·