Altinity / Altinity/clickhouse-operator
Long wait for PVC for Keeper to be created
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 2.6k
- Forks
- 574
- Avg merge
- 8d 6h
- Merged PRs (30d)
- 6
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?
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 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.
Assessment
- Tech stack
- go, helm, kubernetes
- Domain
- databases, devops, infrastructure
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100