b5ca7a6326
* Use lower tablet refresh timeout in vreplication traffic switching And refresh all tablets in dry runs to alert the user to potential issues. * Check primary tablet health in the traffic switcher pre-check * Add msgs about specific tablets that failed refresh to cmd output * Keep function semantics the same but provide details if wanted This keeps the previous behavior of ignoring partial refresh related errors, while providing the defails of WHY we had a partial refresh for anyone that's interested. * Add partial refresh details to response message This way the caller has that info and can decide what to do with it (if anything). * Update tests and vtadmin for updated refresh response message * Cancel switch writes on partial tablet refresh when safe Signed-off-by: Matt Lord <mattalord@gmail.com> |
||
|---|---|---|
| .github | ||
| config | ||
| data/test | ||
| doc | ||
| docker | ||
| examples | ||
| go | ||
| java | ||
| misc | ||
| proto | ||
| resources/bin | ||
| support | ||
| test | ||
| tools | ||
| vitess-mixin | ||
| web | ||
| .codeclimate.yml | ||
| .dockerignore | ||
| .gitignore | ||
| .gitmodules | ||
| .golangci.yml | ||
| ADOPTERS.md | ||
| CODE_OF_CONDUCT.md | ||
| CONTRIBUTING.md | ||
| DCO | ||
| Dockerfile | ||
| GITHUB_SELF_HOSTED_RUNNERS.md | ||
| GOVERNANCE.md | ||
| GUIDING_PRINCIPLES.md | ||
| LICENSE | ||
| MAINTAINERS.md | ||
| Makefile | ||
| README.md | ||
| SECURITY.md | ||
| SEVERITY.md | ||
| STEERING.md | ||
| bootstrap.sh | ||
| build.env | ||
| dev.env | ||
| go.mod | ||
| go.sum | ||
| sonar-project.properties | ||
| test.go | ||
README.md
Vitess
Vitess is a database clustering system for horizontal scaling of MySQL through generalized sharding.
By encapsulating shard-routing logic, Vitess allows application code and database queries to remain agnostic to the distribution of data onto multiple shards. With Vitess, you can even split and merge shards as your needs grow, with an atomic cutover step that takes only a few seconds.
Vitess has been a core component of YouTube's database infrastructure since 2011, and has grown to encompass tens of thousands of MySQL nodes.
For more about Vitess, please visit vitess.io.
Vitess has a growing community. You can view the list of adopters here.
Reporting a Problem, Issue, or Bug
To report a problem, the best way to get attention is to create a GitHub issue using proper severity level based on this guide.
For topics that are better discussed live, please join the Vitess Slack workspace. You may post any questions on the #general channel or join some of the special-interest channels.
Follow Vitess Blog for low-frequency updates like new features and releases.
Security
Reporting Security Vulnerabilities
To report a security vulnerability, please email vitess-maintainers.
See Security for a full outline of the security process.
Security Audit
A third party security audit was performed by Cure53. You can see the full report here.
License
Unless otherwise noted, the Vitess source files are distributed under the Apache Version 2.0 license found in the LICENSE file.
