planetscale / planetscale/vitess-operator
etcd cannot start
Open
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 372
- Forks
- 102
- Avg merge
- 3d 5h
- Merged PRs (30d)
- 15
Description
i use vitess-operator. there is problem with etcd from logs
Events:
Type Reason Age From Message
---- ------ ---- ---- -------
Normal Scheduled 29s default-scheduler Successfully assigned default/example-etcd-faf13de3-1 to elastic-01
Normal Pulled 30s kubelet Container image "quay.io/coreos/etcd:v3.3.13" already present on machine
Normal Created 29s kubelet Created container etcd
Normal Started 29s kubelet Started container etcd
Warning Unhealthy 5s (x4 over 20s) kubelet Readiness probe failed: 127.0.0.1:2379 is unhealthy: failed to commit proposal: context deadline exceeded
Error: unhealthy cluster
how to fix it,
thank you
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 with the reported etcd pod events and readiness-probe failure, then inspect how the Vitess Operator configures the etcd cluster and probe. Reproduce the unhealthy-cluster condition and identify a documented configuration or code-level cause; done means etcd starts successfully and the readiness probe passes.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- kubernetes
- Domain
- devops, distributed-systems, infrastructure
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100