. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 86 Multi-schema . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 115 Multi-cell . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . long_query_time NoOp low_priority_updates NoOp max_delayed_threads NoOp max_insert_delayed_threads NoOp multi_range_count NoOp net_buffer_length NoOp new NoOp query_cache_type NoOp query_cache_wlock_invalidate

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63 Introduction 64 Features 64 Multi-schema . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 95 Multi-cell . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 458 Multi-Column Vindexes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56 3 Introduction 56 Features 56 Multi-schema . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 81 Multi-cell . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . long_query_time NoOp low_priority_updates NoOp max_delayed_threads NoOp max_insert_delayed_threads NoOp multi_range_count NoOp net_buffer_length NoOp new NoOp query_cache_type NoOp query_cache_wlock_invalidate

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61 Introduction 61 Features 61 Multi-schema . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 91 Multi-cell . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . long_query_time NoOp low_priority_updates NoOp max_delayed_threads NoOp max_insert_delayed_threads NoOp multi_range_count NoOp net_buffer_length NoOp new NoOp query_cache_type NoOp query_cache_wlock_invalidate

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42 Multi-cell . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . SINGLE: disallow multi-db transactions. • MULTI: multi-db transactions with best effort commit. • TWOPC: multi-db transactions with 2PC commit. No multi-master Vitess doesn’t support multi-master setup. ways of addressing most of the use cases that are typically solved by multi-master: • Scalability: There are situations where multi-master gives you a little bit of additional runway. However, since the

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37 Multi-cell . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . SINGLE: disallow multi-db transactions. • MULTI: multi-db transactions with best effort commit. • TWOPC: multi-db transactions with 2PC commit. 37 No multi-master Vitess doesn’t support multi-master setup ways of addressing most of the use cases that are typically solved by multi-master: • Scalability: There are situations where multi-master gives you a little bit of additional runway. However, since the

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45 Multi-cell . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . SINGLE: disallow multi-db transactions. • MULTI: multi-db transactions with best effort commit. • TWOPC: multi-db transactions with 2PC commit. No multi-master Vitess doesn’t support multi-master setup. ways of addressing most of the use cases that are typically solved by multi-master: • Scalability: There are situations where multi-master gives you a little bit of additional runway. However, since the

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54 Multi-cell . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . long_query_time NoOp low_priority_updates NoOp max_delayed_threads NoOp max_insert_delayed_threads NoOp multi_range_count NoOp net_buffer_length NoOp new NoOp query_cache_type NoOp query_cache_wlock_invalidate SINGLE: disallow multi-db transactions. • MULTI: multi-db transactions with best effort commit. • TWOPC: multi-db transactions with 2PC commit. No multi-master Vitess doesn’t support multi-master setup.

row-cache • limit inefficiency SQL • more client connection • replication lag optimization • multi data center Vitess Topo Vitess concepts • keyspace/keyspaceId • vtctl • vttablet • vtgate • vttablet • prepare two spare shard0, shard1 • vtgate point to origin master • multi-snapshot : data & repl-pos • multi-restore • set shard0, shard1 read-only. • shard0, shard1 replication to orign

Replica Replica Replica Replica Replica Replica Replica Replica Replica Zone 1 Zone 2 Zone 3 Multi-zone Isolation