These are: • utf8 • utf8mb4 • ascii • binary To be able to work with other character sets: • Verify VReplication supports the specific character sets. • VReplication needs to be told how which character Waiting for vtgate to be up... vtgate is up! Access vtgate at http://askdba:15001/debug/status Verify your initial cluster: $ mysql -e "show vitess_tablets" +-------+----------+-------+------------ ----+------------+---------+------------------+-----------+----------------------+ You can also verify that the processes have started with pgrep: $ pgrep -fl vtdataroot | awk '{print $2,$3}' etcd --enable

vtgate to be up... vtgate is up! Access vtgate at http://localhost:15001/debug/status You can also verify that the processes have started with pgrep: ~/my-vitess -example > pgrep -fl vtdataroot 3920 etcd /app/ vtgate: http://localhost:8001/api/v1/namespaces/default/services/vtgate-zone1:web/proxy/ Verify cluster You can check the state of your cluster with kubectl get pods,jobs. After a few minutes, -0000000100 is not a master in the shard, proceeding anyway as -force was used .. You can also verify that the processes have started with pgrep: ~/my-vitess -example > pgrep -fl vtdataroot 14119 etcd

/app/ vtgate: http://localhost:8001/api/v1/namespaces/default/services/vtgate-zone1:web/proxy/ Verify cluster You can check the state of your cluster with kubectl get pods,jobs. After a few minutes, -0000000100 is not a master in the shard, proceeding anyway as -force was used .. 74 You can also verify that the processes have started with pgrep: ~/my-vitess -example > pgrep -fl vtdataroot 14119 etcd yaml. Once vtorc is officially released, the examples will be updated accordingly. {{< /info >}} Verify cluster You can check the state of your cluster with kubectl get pods. After a few minutes, it should

/app/ vtgate: http://localhost:8001/api/v1/namespaces/default/services/vtgate-zone1:web/proxy/ Verify cluster You can check the state of your cluster with kubectl get pods,jobs. After a few minutes, Waiting for vtgate to be up... vtgate is up! Access vtgate at http://askdba:15001/debug/status Verify your initial cluster: $ mysql -e "show vitess_tablets" +-------+----------+-------+------------ ----+------------+---------+------------------+-----------+----------------------+ You can also verify that the processes have started with pgrep: $ pgrep -fl vtdataroot | awk '{print $2,$3}' etcd --enable

/app/ vtgate: http://localhost:8001/api/v1/namespaces/default/services/vtgate-zone1:web/proxy/ Verify cluster You can check the state of your cluster with kubectl get pods,jobs. After a few minutes, Waiting for vtgate to be up... vtgate is up! Access vtgate at http://askdba:15001/debug/status Verify your initial cluster: $ mysql -e "show vitess_tablets" +-------+----------+-------+------------ +------------+---------+------------------+-----------+----------------------+ 78 You can also verify that the processes have started with pgrep: $ pgrep -fl vtdataroot | awk '{print $2,$3}' etcd --enable

also lets you easily add other validation procedures. You could do in-tablet integrity checks to verify foreign-key-like relationships or cross-shard integrity checks if, for example, an index table in /app/ vtgate: http://localhost:8001/api/v1/namespaces/default/services/vtgate-zone1:web/proxy/ Verify cluster You can check the state of your cluster with kubectl get pods,jobs. After a few minutes, -0000000100 is not a master in the shard, proceeding anyway as -force was used .. You can also verify that the processes have started with pgrep: ~/my-vitess -example > pgrep -fl vtdataroot 14119 etcd

also lets you easily add other validation procedures. You could do in-tablet integrity checks to verify foreign-key-like relationships or cross-shard integrity checks if, for example, an index table in /app/ vtgate: http://localhost:8001/api/v1/namespaces/default/services/vtgate-zone1:web/proxy/ Verify cluster You can check the state of your cluster with kubectl get pods,jobs. After a few minutes, -0000000100 is not a master in the shard, proceeding anyway as -force was used .. You can also verify that the processes have started with pgrep: 32 ~/my-vitess -example > pgrep -fl vtdataroot 14119

also lets you easily add other validation procedures. You could do in-tablet integrity checks to verify foreign-key-like relationships or cross-shard integrity checks if, for example, an index table in 101_initial_cluster.yaml This will bring up the initial Vitess cluster with a single keyspace. Verify cluster Once successful, you should see the following state: $ kubectl get pods,jobs NAME READY is done, the customer and corder tables are no longer accessible in the commerce keyspace. You can verify this by trying to read from them. ./kmysql.sh --table < ../common/select_commerce_data.sql Using

are always run against the latest Vitess commit. This build cycle happens daily and OSS-Fuzz will verify if any existing bugs have been fixed. If OSS-fuzz finds that any bugs have been fixed OSS-Fuzz marks and OSS-Fuzz will pull the latest Vitess master branch the next time it performs a fuzz run and verify that a given issue has been fixed. Vitess's fuzzers reside in CNCF's dedicated fuzzing repository compliance. Vitess manages its source code on Github which makes it version controlled and possible to verify the commit history. The source code is retained indefinitely and all commits are verified by two