Long wait for PVC for Keeper to be created
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 35/100
- Issue type
- Bug
- Clarity
- Needs clarification
- Activity status
- Stale
- Tech stack
- go, helm, kubernetes
- Domain
- databases, devops, infrastructure
Research direction
Start by reproducing CHI and CHKI creation with clickhouse-operator 0.25.4 deployed through the Helm chart, then inspect Keeper PVC creation and Kubernetes scheduling events. The investigation is complete when the cause of the delayed final PVC is identified and all Keeper PVCs are created without the reported missing-PVC scheduling message.
Written by the indexing model from the issue text.
Description
Hi,
I use clickhouse-operator 0.25.4 deployed with Helm Chart, when creating new CHI and CHKI I need to wait long time till the PVCs for Keeper are created.
It keeps waiting for PVC for one of Keeper instances, two are created instantly, the last one after around 15 minutes.
Unit operator creates last PVC the pod for this one instance returns:
0/9 nodes are available: persistentvolumeclaim "keeper-0-keeper-clickhouse-0-0" not found. preemption: 0/9 nodes are available: 9 Preemption is not helpful for scheduling.
Did you know what happens?
- Dominant language
- Go
- Stars
- 2.6k
- Forks
- 579
- Avg merge
- 5d 22h
- Merged PRs (30d)
- 5
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
-
CHK reconciles in a tight loop after its first Completed; with `onKeeperResourceUpdate: reconcile` the dependent CHI never finishes (0.27.4)Possibly taken A pull request linked to this issue is open or already merged. Open
Difficulty 5/5 Over a week Newbie friendliness 12/100
Altinity/clickhouse-operator#2107 ·
Maintainers usually reply within 1 day
-
Recover reconciles from recoverAbortedReconcileOnPodReady ignores readiness of service selector labelsPossibly taken @Tyagiquamar claimed this 3 days ago. Open
Difficulty 4/5 3-5 days Newbie friendliness 35/100
Altinity/clickhouse-operator#2106 ·
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
All issues in Altinity/clickhouse-operator
Similar issues
-
usage: a custom provider's balance meters ("…%" in the balance path) ignore the Left/Used switchOpen
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
Maintainers usually reply within 1 day
-
bug iam-service
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
platform-mesh/platform-mesh#425 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
grafana/tempo-operator#1691 ·
Maintainers usually reply within 1 day
-
fix: presentation.go with mcp-table.go: the message for each MCP server comes backPossibly taken @mge1512 claimed this today. Openbug
Difficulty 1/5 1-3 hours Newbie friendliness 78/100
mark3labs/kit#242 · 1 comment ·
Maintainers usually reply within 1 day
-
Difficulty 1/5 Under an hour Newbie friendliness 85/100
slavakurilyak/awesome-ai-agents#827 ·
Maintainers usually reply within 1 day