auto_increment_increment NotSupported auto_increment_offset NotSupported binlog_direct_non_transactional_updates NotSupported binlog_row_image NotSupported binlog_rows_query_log_events NotSupported 21 System variable transaction_prealloc_size ReservedConn unique_checks ReservedConn updatable_views_with_limit ReservedConn binlog_format CheckAndIgnore block_encryption_mode CheckAndIgnore character_set_client CheckAndIgnore c com/vitessio/website/pull/512) • We can SET SQL_LOG_BIN=0 and only purge the table on the primary. This reduces binlog size and also does not introduce replication lag. One may argue that lag-based throttling is not

auto_increment_increment NotSupported auto_increment_offset NotSupported binlog_direct_non_transactional_updates NotSupported binlog_row_image NotSupported binlog_rows_query_log_events NotSupported innodb_ft_enable_stopword transaction_prealloc_size ReservedConn unique_checks ReservedConn updatable_views_with_limit ReservedConn binlog_format CheckAndIgnore block_encryption_mode CheckAndIgnore character_set_client CheckAndIgnore c com/vitessio/website/pull/512) • We can SET SQL_LOG_BIN=0 and only purge the table on the primary. This reduces binlog size and also does not introduce replication lag. One may argue that lag-based throttling is not

auto_increment_increment NotSupported auto_increment_offset NotSupported binlog_direct_non_transactional_updates NotSupported binlog_row_image NotSupported binlog_rows_query_log_events NotSupported innodb_ft_enable_stopword transaction_prealloc_size ReservedConn unique_checks ReservedConn updatable_views_with_limit ReservedConn binlog_format CheckAndIgnore block_encryption_mode CheckAndIgnore character_set_client CheckAndIgnore c com/vitessio/website/pull/512) • We can SET SQL_LOG_BIN=0 and only purge the table on the primary. This reduces binlog size and also does not introduce replication lag. One may argue that lag-based throttling is not

auto_increment_increment NotSupported auto_increment_offset NotSupported binlog_direct_non_transactional_updates NotSupported binlog_row_image NotSupported binlog_rows_query_log_events NotSupported innodb_ft_enable_stopword transaction_prealloc_size ReservedConn unique_checks ReservedConn updatable_views_with_limit ReservedConn binlog_format CheckAndIgnore block_encryption_mode CheckAndIgnore character_set_client CheckAndIgnore c allows you to loosen some of the disk-based durability settings. For example, you can turn off sync_binlog, which greatly reduces the number of IOPS to the disk thereby increasing effective throughput. Consistency

auto_increment_increment NotSupported auto_increment_offset NotSupported binlog_direct_non_transactional_updates NotSupported binlog_row_image NotSupported binlog_rows_query_log_events NotSupported innodb_ft_enable_stopword transaction_prealloc_size ReservedConn unique_checks ReservedConn updatable_views_with_limit ReservedConn binlog_format CheckAndIgnore block_encryption_mode CheckAndIgnore 27 System variable Handled character_set_client com/vitessio/website/pull/512) • We can SET SQL_LOG_BIN=0 and only purge the table on the primary. This reduces binlog size and also does not introduce replication lag. One may argue that lag-based throttling is not

allows you to loosen some of the disk-based durability settings. For example, you can turn off sync_binlog, which greatly reduces the number of IOPS to the disk thereby increasing effective throughput. Consistency the use of Row-Based Replication with GTIDs enabled. In addition, Vitess only supports the default binlog_row_image of FULL. {{< /warning >}} Vitess makes use of MySQL Replication for both high availability be simple enough that the materialized table can be kept up-to-date from the data coming from the binlog. For example, joins are not supported. • Correctness verification (to be implemented): VReplication

pulls events from the binlog. This would allow for efficient execution of processes such as VReplication where a subscriber can indirectly receive and apply events from the binlog. A user can apply filtering allows you to loosen some of the disk-based durability settings. For example, you can turn off sync_binlog, which greatly reduces the number of IOPS to the disk thereby increasing effective throughput. 44 the use of Row-Based Replication with GTIDs enabled. In addition, Vitess only supports the default binlog_row_image of FULL. {{< /warning >}} Vitess makes use of MySQL Replication for both high availability

allows you to loosen some of the disk-based durability settings. For example, you can turn off sync_binlog, which greatly reduces the number of IOPS to the disk thereby increasing effective throughput. Consistency the use of Row-Based Replication with GTIDs enabled. In addition, Vitess only supports the default binlog_row_image of FULL. {{< /warning >}} Vitess makes use of MySQL Replication for both high availability retrieved from vttablet when executing a query. It is also sent with the replication streams from the binlog service. Properties Name Description timestamp int64 timestamp is the MySQL timestamp of the statements

DeleteUnsharded DeleteEqual InsertUnsharded InsertSharded Vttablet • User Auth • SQL Filter • Binlog Filter • Backup • Restore • Diffs • Row Limit • Kill Timeout SQL • Query blacklisting • row • write manifest & gzip Vitess RowCache • RowCache VS MySQL Buffer Pool • LRUCache • Base on binlog • DDL ? • key=prefix +body • every DDL —> prefix:=prefix+1 • lastest prefix + Body • vttable