. . . . . . . . . . . . 27 I cannot start a cluster, and see these errors in the logs: Could not open required defaults file: /path/to/my.cnf . 27 Queries . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 251 2. Identify a VSchema for the statement’s source tables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 252 3. Run the VTExplain (splitting or merging shards), there can be shards with overlapping key ranges. For example, the source shard of a split may serve c0-d0 while its destination shards serve c0-c8 and c8-d0 respectively

. . . . . . . . . . . . 26 I cannot start a cluster, and see these errors in the logs: Could not open required defaults file: /path/to/my.cnf . 26 Queries . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 207 2. Identify a VSchema for the statement’s source tables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 207 3. Run the VTExplain (splitting or merging shards), there can be shards with overlapping key ranges. For example, the source shard of a split may serve c0-d0 while its destination shards serve c0-c8 and c8-d0 respectively

. . . . . . . . . . . . 22 I cannot start a cluster, and see these errors in the logs: Could not open required defaults file: /path/to/my.cnf . 23 Queries . . . . . . . . . . . . . . . . . . . . . . (splitting or merging shards), there can be shards with overlapping key ranges. For example, the source shard of a split may serve c0-d0 while its destination shards serve c0-c8 and c8-d0 respectively pieces, or merging neighboring shards into bigger pieces. During dynamic resharding, the data in the source shards is copied into the destination shards, allowed to catch up on replication, and then compared

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 290 Drop source . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . smaller pieces, or merging neighboring shards into bigger pieces. During resharding, the data in the source shards is copied into the destination shards, allowed to catch up on replication, and then compared data integrity. Then the live serving infrastructure is shifted to the destination shards, and the source shards are deleted. Related Vitess Documentation • Resharding User Guide Tablet A tablet is a

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 266 Source Metrics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 332 Drop source . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 453 2. Identify a VSchema for the statement’s source tables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 454 3. Run the VTExplain

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 252 Source Metrics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 310 Drop source . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . smaller pieces, or merging neighboring shards into bigger pieces. During resharding, the data in the source shards is copied into the destination shards, allowed to catch up on replication, and then compared

. . . . . . . . . . . . 39 I cannot start a cluster, and see these errors in the logs: Could not open required defaults file: /path/to/my.cnf . 40 Queries . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 250 Drop source . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . provides aliases for mysql and vtctlclient. These are automatically created when you start the cluster. source ./env.sh 17 Setting up aliases changes mysql to always connect to Vitess for your current session

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 291 Source Metrics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 355 Drop source . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . smaller pieces, or merging neighboring shards into bigger pieces. During resharding, the data in the source shards is copied into the destination shards, allowed to catch up on replication, and then compared

PRESENTS Vitess security audit In collaboration with the Vitess maintainers, Open Source Technology Improvement Fund and The Linux Foundation Authors Adam Korczynski David Korczynski Adam@adalogics.com David Korczynski Security Researcher, Ada Logics David@adalogics.com The Vitess community members involved in audit were: Name Title Email Deepthi Sigireddi Project Lead & Maintainer Deepthi@planetscale modelling: ● Vitessʼs documentation including README files from the Vitess repository ● Vitessʼs source code at https://github.com/vitessio/vitess ● Feedback from Vitess maintainers The threat model

Kubernetes Production launch Last Sunday... Vitess Kubernetes users Some wish to be unnamed The Community In production Evaluating Quiz of Kings Architecture shard n shard 1 vtgate app server app