row limit per query. What if I want to do a full table scan? Vitess supports different modes. In OLTP mode, the result size is typically limited to a preset number (10 000 rows by default). This limit used judiciously as it supersedes shutdown and reparent commands. The general convention is to send OLTP queries to REPLICA tablet types, and OLAP queries to RDONLY. Is there a list of supported/unsupported master, one replica and one rdonly vttablets. 26 The purpose of a replica tablet is for serving OLTP read traffic, whereas rdonly tablets are for serving analytics, or performing cluster maintenance

row limit per query. What if I want to do a full table scan? Vitess supports different modes. In OLTP mode, the result size is typically limited to a preset number (10 000 rows by default). This limit used judiciously as it supersedes shutdown and reparent commands. The general convention is to send OLTP queries to REPLICA tablet types, and OLAP queries to RDONLY. Is there a list of supported/unsupported code paths that can tolerate slightly stale data, the queries should be sent to REPLICA tablets for OLTP, and RDONLY tablets for OLAP workloads. This allows you to scale your read traffic more easily, and

row limit per query. What if I want to do a full table scan? Vitess supports different modes. In OLTP mode, the result size is typically limited to a preset number (10 000 rows by default). This limit used judiciously as it supersedes shutdown and reparent commands. The general convention is to send OLTP queries to REPLICA tablet types, and OLAP queries to RDONLY. Is there a list of supported/unsupported code paths that can tolerate slightly stale data, the queries should be sent to REPLICA tablets for OLTP, and RDONLY tablets for OLAP workloads. This allows you to scale your read traffic more easily, and

apply to queries that are exceeding this time limit. This limit applies to all queries: streaming, oltp read, reserved, and in_transaction. • The transaction shutdown code “waits for empty”, but reserved -config-transaction -prefill -parallelism maxWaiters: 50000 # queryserver -config-txpool-waiter-cap oltp: queryTimeoutSeconds: 30 # queryserver -config-query-timeout txTimeoutSeconds: 30 # queryserver -config-transaction code paths that can tolerate slightly stale data, the queries should be sent to REPLICA tablets for OLTP, and RDONLY tablets for OLAP workloads. This allows you to scale your read traffic more easily, and

apply to queries that are exceeding this time limit. This limit applies to all queries: streaming, oltp read, reserved, and in_transaction. • The transaction shutdown code “waits for empty”, but reserved -config-transaction -prefill -parallelism maxWaiters: 50000 # queryserver -config-txpool-waiter-cap oltp: queryTimeoutSeconds: 30 # queryserver -config-query-timeout txTimeoutSeconds: 30 # queryserver -config-transaction code paths that can tolerate slightly stale data, the queries should be sent to REPLICA tablets for OLTP, and RDONLY tablets for OLAP workloads. This allows you to scale your read traffic more easily, and

row limit per query. What if I want to do a full table scan? Vitess supports different modes. In OLTP mode, the result size is typically limited to a preset number (10 000 rows by default). This limit used judiciously as it supersedes shutdown and reparent commands. The general convention is to send OLTP queries to REPLICA tablet types, and OLAP queries to RDONLY. Is there a list of supported/unsupported code paths that can tolerate slightly stale data, the queries should be sent to REPLICA tablets for OLTP, and RDONLY tablets for OLAP workloads. This allows you to scale your read traffic more easily, and

apply to queries that are exceeding this time limit. This limit applies to all queries: streaming, oltp read, reserved, and in_transaction. • The transaction shutdown code “waits for empty”, but reserved -config-transaction -prefill -parallelism maxWaiters: 50000 # queryserver -config-txpool-waiter-cap oltp: queryTimeoutSeconds: 30 # queryserver -config-query-timeout txTimeoutSeconds: 30 # queryserver -config-transaction code paths that can tolerate slightly stale data, the queries should be sent to REPLICA tablets for OLTP, and RDONLY tablets for OLAP workloads. This allows you to scale your read traffic more easily, and

apply to queries that are exceeding this time limit. This limit applies to all queries: streaming, oltp read, reserved, and in_transaction. • The transaction shutdown code “waits for empty”, but reserved -config-transaction -prefill -parallelism maxWaiters: 50000 # queryserver -config-txpool-waiter-cap oltp: queryTimeoutSeconds: 30 # queryserver -config-query-timeout txTimeoutSeconds: 30 # queryserver -config-transaction code paths that can tolerate slightly stale data, the queries should be sent to REPLICA tablets for OLTP, and RDONLY tablets for OLAP workloads. This allows you to scale your read traffic more easily, and