planetscale / planetscale/vitess-operator
how to restore a cluster in case of failure
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 372
- Forks
- 102
- Avg merge
- 3d 5h
- Merged PRs (30d)
- 15
Description
Hello. Very interesting solution. I have a MySQL server s 3 slave behaves very badly because of this we are looking for a shard solution because the data already reaches 6 TB. I liked Vitess, and the solution on K8S Vitess-operator, although I have not yet been able to fully understand how to do it correctly. I have several questions.
- why Deployment and not Stateful?
- how to restore a cluster in case of failure?
- how to properly configure the MySQL server config that Vtablet runs or does it happen automatically?
- for vtablet I made pv with node affinity like a hotel, but the operator created a few pv for other components automatically, can I control them too?
- in the latest version of “external source” there is an error, but v19. gets connected.
I must say the Vitess documents are good, but the Vitess operator documents are not so good at all.
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
No file, test, or entry point is named in the issue. Start by reviewing the Vitess Operator documentation for cluster recovery, StatefulSets, MySQL configuration, persistent volumes, and external sources. Done means documenting resolved answers and supported procedures for each question.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- kubernetes, mysql
- Domain
- databases, devops, documentation
- Issue type
- Documentation
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100