conventions / style? Linter was run and is happy? • Does this match our current patterns? Example include RPC patterns, Retries / Waits / Timeouts patterns using Context, … Additionally, we recommend that every messages that are older than 86400 seconds (1 day). • vt_batch_size=10: Send up to 10 messages per RPC packet. • vt_cache_size=10000: Store up to 10000 messages in the cache. If the demand is higher, the will come at a higher latency cost and very low throughput. We never use the Topology Service as an RPC or queuing mechanism or as a storage system for logs. We never depend on the Topology Service being

of bad transient state or bad user queries) * Does this match our current patterns? Example include RPC patterns, Retries / Waits / Timeouts patterns using Context, … We also recommend that every author messages that are older than 86400 seconds (1 day). • vt_batch_size=10: Send up to 10 messages per RPC packet. • vt_cache_size=10000: Store up to 10000 messages in the cache. If the demand is higher, the will come at a higher latency cost and very low throughput. We never use the Topology Service as an RPC or queuing mechanism or as a storage system for logs. We never depend on the Topology Service being

bad transient state or bad user queries) • Does this match our current patterns? Example include RPC patterns, Retries / Waits / Timeouts patterns using Context, … We also recommend that every author While vttablet is up Every flow that needs to change something about a tablet directly issues an rpc request to it. The tablet will immediately execute the request, and will perform a best-effort action messages that are older than 86400 seconds (1 day). • vt_batch_size=10: Send up to 10 messages per RPC packet. • vt_cache_size=10000: Store up to 10000 messages in the cache. If the demand is higher, the

bad transient state or bad user queries) • Does this match our current patterns? Example include RPC patterns, Retries / Waits / Timeouts patterns using Context, … We also recommend that every author While vttablet is up Every flow that needs to change something about a tablet directly issues an rpc request to it. The tablet will immediately execute the request, and will perform a best-effort action messages that are older than 86400 seconds (1 day). • vt_batch_size=10: Send up to 10 messages per RPC packet. • vt_cache_size=10000: Store up to 10000 messages in the cache. If the demand is higher, the

bad transient state or bad user queries) • Does this match our current patterns? Example include RPC patterns, Retries / Waits / Timeouts patterns using Context, … We also recommend that every author While vttablet is up Every flow that needs to change something about a tablet directly issues an rpc request to it. The tablet will immediately execute the request, and will perform a best-effort action messages that are older than 86400 seconds (1 day). • vt_batch_size=10: Send up to 10 messages per RPC packet. • vt_cache_size=10000: Store up to 10000 messages in the cache. If the demand is higher, the

bad transient state or bad user queries) • Does this match our current patterns? Example include RPC patterns, Retries / Waits / Timeouts patterns using Context, … We also recommend that every author While vttablet is up Every flow that needs to change something about a tablet directly issues an rpc request to it. The tablet will immediately execute the request, and will perform a best-effort action pacity • vttablet user flag: -db_dba_user (default ‘vt_dba’) • Used by vttablet ExecuteFetchAsDba RPC. This is used when using vtctlclient ExecuteFetchAsDba Also used implic- itly for various internal

conventions / style? Linter was run and is happy? • Does this match our current patterns? Example include RPC patterns, Retries / Waits / Timeouts patterns using Context, … Additionally, we recommend that every commerce.0.master , used tablet: zone1 -1564760600 (zone1-commerce -0-replica -0.vttablet), vttablet: rpc error: code = FailedPrecondition desc = disallowed due to rule: enforce blacklisted tables (CallerID: commerce.0.master , used tablet: zone1 -1564760600 (zone1-commerce -0-replica -0.vttablet), vttablet: rpc error: code = InvalidArgument desc = table customer not found in schema (CallerID: userData1) Horizontal

conventions / style? Linter was run and is happy? • Does this match our current patterns? Example include RPC patterns, Retries / Waits / Timeouts patterns using Context, … Additionally, we recommend that every messages that are older than 86400 seconds (1 day). • vt_batch_size=10: Send up to 10 messages per RPC packet. • vt_cache_size=10000: Store up to 10000 messages in the cache. If the demand is higher, the will come at a higher latency cost and very low throughput. We never use the Topology Service as an RPC or queuing mechanism or as a storage system for logs. We never depend on the Topology Service being

developer tools, we see we get an error: HttpResponseNotOkError: [status 500] /api/keyspaces: unknown rpc error: code = Unknown desc = node doesn't exist: /vitess/global/keyspaces/KEYSPACE_NAME/Keyspace If