_table NotSupported ndb_autoincrement_prefetch_sz NotSupported ndb_blob_read_batch_bytes NotSupported ndb_blob_write_batch_bytes NotSupported ndb_deferred_constraints NotSupported ndb_force_send NotSupported MySQL replica that cannot be promoted to master. Conventionally, these are used for background processing jobs, such as taking backups, dumping data to other systems, heavy analytical queries, MapReduce T2: DDL 2 on table1 T3: Version Event DDL1 // gets written because of the time taken by tracker processing DDL1 T4: DML1 on table1 T5: Version Event DDL2 // gets written AFTER DML1 So now on the replica

_table NotSupported ndb_autoincrement_prefetch_sz NotSupported ndb_blob_read_batch_bytes NotSupported ndb_blob_write_batch_bytes NotSupported ndb_deferred_constraints NotSupported ndb_force_send NotSupported MySQL replica that cannot be promoted to master. Conventionally, these are used for background processing jobs, such as taking backups, dumping data to other systems, heavy analytical queries, MapReduce T2: DDL 2 on table1 T3: Version Event DDL1 // gets written because of the time taken by tracker processing DDL1 T4: DML1 on table1 T5: Version Event DDL2 // gets written AFTER DML1 So now on the replica

A MySQL slave that cannot be promoted to master. Conventionally, these are used for background processing jobs, such as taking backups, dumping data to other systems, heavy analytical queries, MapReduce 2m44s NAME COMPLETIONS DURATION AGE job.batch/commerce -apply-schema-initial 1/1 118s 2m44s job.batch/commerce -apply-vschema -initial 1/1 109s 2m44s job.batch/zone1-commerce -0-init-shard-master 1/1 profile is mostly reads, this works really well. • Not all cells need rdonly (or batch) instances. Only the cells that run batch jobs, or OLAP jobs, really need them. Note Vitess uses local-cell data first

_table NotSupported ndb_autoincrement_prefetch_sz NotSupported ndb_blob_read_batch_bytes NotSupported ndb_blob_write_batch_bytes NotSupported ndb_deferred_constraints NotSupported ndb_force_send NotSupported MySQL replica that cannot be promoted to master. Conventionally, these are used for background processing jobs, such as taking backups, dumping data to other systems, heavy analytical queries, MapReduce T2: DDL 2 on table1 T3: Version Event DDL1 // gets written because of the time taken by tracker processing DDL1 T4: DML1 on table1 T5: Version Event DDL2 // gets written AFTER DML1 So now on the replica

A MySQL slave that cannot be promoted to master. Conventionally, these are used for background processing jobs, such as taking backups, dumping data to other systems, heavy analytical queries, MapReduce 2m21s NAME COMPLETIONS DURATION AGE job.batch/commerce -apply-schema-initial 1/1 106s 2m21s job.batch/commerce -apply-vschema -initial 1/1 101s 2m21s job.batch/zone1-commerce -0-init-shard-master 1/1 profile is mostly reads, this works really well. • Not all cells need rdonly (or batch) instances. Only the cells that run batch jobs, or OLAP jobs, really need them. Note Vitess uses local-cell data first

_table NotSupported ndb_autoincrement_prefetch_sz NotSupported ndb_blob_read_batch_bytes NotSupported ndb_blob_write_batch_bytes NotSupported ndb_deferred_constraints NotSupported ndb_force_send NotSupported MySQL replica that cannot be promoted to master. Conventionally, these are used for background processing jobs, such as taking backups, dumping data to other systems, heavy analytical queries, MapReduce 2m42s NAME COMPLETIONS DURATION AGE job.batch/commerce -apply-schema-initial 1/1 94s 2m43s job.batch/commerce -apply-vschema -initial 1/1 87s 2m43s job.batch/zone1-commerce -0-init-shard-master 1/1 90s

MySQL replica that cannot be promoted to master. Conventionally, these are used for background processing jobs, such as taking backups, dumping data to other systems, heavy analytical queries, MapReduce 2m42s NAME COMPLETIONS DURATION AGE job.batch/commerce -apply-schema-initial 1/1 94s 2m43s job.batch/commerce -apply-vschema -initial 1/1 87s 2m43s job.batch/zone1-commerce -0-init-shard-master 1/1 90s profile is mostly reads, this works really well. • Not all cells need rdonly (or batch) instances. Only the cells that run batch jobs, or OLAP jobs, really need them. Note Vitess uses local-cell data first

_table NotSupported ndb_autoincrement_prefetch_sz NotSupported ndb_blob_read_batch_bytes NotSupported ndb_blob_write_batch_bytes NotSupported ndb_deferred_constraints NotSupported ndb_force_send NotSupported MySQL replica that cannot be promoted to primary. Conventionally, these are used for background processing jobs, such as taking backups, dumping data to other systems, heavy analytical queries, MapReduce Vttablet. The output of the parser is stored in a Abstract Syntax Tree which is used for further processing by the planner. The code for the parser and AST lives here. Parser Vitess uses a yacc-based

extensive fuzzing work; It carried out a fuzzing audit in 2020 which added coverage to complex text processing routines. Vitess is integrated into OSS-Fuzz which allows the fuzzers to run continuously and notify