Skip to content
main
Switch branches/tags
Code

Latest commit

* Improved schema tracking E2E test with PRS

Signed-off-by: Florent Poinsard <florent.poinsard@outlook.fr>

* Keep track of current tablet information everytime we receive a healthcheck response

Signed-off-by: Florent Poinsard <florent.poinsard@outlook.fr>

* Use the target tablet type in the update_controller of schema tracking

Signed-off-by: Florent Poinsard <florent.poinsard@outlook.fr>

* Add new E2E test to config.json

Signed-off-by: Florent Poinsard <florent.poinsard@outlook.fr>

* Remove fix in the healthcheck

Signed-off-by: Florent Poinsard <florent.poinsard@outlook.fr>

* reduced the size of cluster in schema tracking PRS sharded E2E test

Signed-off-by: Florent Poinsard <florent.poinsard@outlook.fr>

* Do not test TestAddColumn is vtgate < v14

Signed-off-by: Florent Poinsard <florent.poinsard@outlook.fr>

* Retry waitForVTGateAndVTTablet when WaitForTabletsToHealthyInVtgate returns an error

Signed-off-by: Florent Poinsard <florent.poinsard@outlook.fr>
4214b41

Files

Permalink
Failed to load latest commit information.
Type
Name
Latest commit message
Commit time
 
 
 
 
 
 
doc
 
 
 
 
 
 
go
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
web
 
 
 
 
 
 
 
 
DCO
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 

Maven Central Build Status codebeat badge Go Report Card FOSSA Status CII Best Practices Coverage

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.

FOSSA Status