data and provide a distributed locking service. Vitess uses a plug-in system to support various backends for storing topology data, which are assumed to provide a distributed, consistent key-value store external reparents. emit_stats boolean true iff we should emit stats to push-based monitoring/stats backends grpc_auth_mode string Which auth plugin implementation to use (eg: static) grpc_auth_mtls_allowed_substrings exported variables. stats_emit_period duration Interval between emitting stats to all registered backends (default 1m0s) stderrthreshold value logs at or above this threshold go to stderr (default 1) tablet_dir

data and provide a distributed locking service. Vitess uses a plug-in system to support various backends for storing topology data, which are assumed to provide a distributed, consistent key-value store external reparents. emit_stats boolean true iff we should emit stats to push-based monitoring/stats backends grpc_auth_mode string Which auth plugin implementation to use (eg: static) grpc_auth_mtls_allowed_substrings exported variables. stats_emit_period duration Interval between emitting stats to all registered backends (default 1m0s) stderrthreshold value logs at or above this threshold go to stderr (default 1) tablet_dir

data and provide a distributed locking service. Vitess uses a plug-in system to support various backends for storing topology data, which are assumed to provide a distributed, consistent key-value store external reparents. emit_stats boolean true iff we should emit stats to push-based monitoring/stats backends grpc_auth_mode string Which auth plugin implementation to use (eg: static) grpc_auth_mtls_allowed_substrings exported variables. stats_emit_period duration Interval between emitting stats to all registered backends (default 1m0s) stderrthreshold value logs at or above this threshold go to stderr (default 1) tablet_dir

data and provide a distributed locking service. Vitess uses a plug-in system to support various backends for storing topology data, which are assumed to provide a distributed, consistent key-value store Type Definition emit_stats boolean true iff we should emit stats to push-based monitoring/stats backends grpc_auth_mode string Which auth plugin implementation to use (eg: static) grpc_auth_mtls_allowed_substrings exported variables. stats_emit_period duration Interval between emitting stats to all registered backends (default 1m0s) stderrthreshold value logs at or above this threshold go to stderr (default 1) tablet_dir

data and provide a distributed locking service. Vitess uses a plug-in system to support various backends for storing topology data, which are assumed to provide a distributed, consistent key-value store Type Definition emit_stats boolean true iff we should emit stats to push-based monitoring/stats backends grpc_auth_mode string Which auth plugin implementation to use (eg: static) grpc_auth_mtls_allowed_substrings exported variables. stats_emit_period duration Interval between emitting stats to all registered backends (default 1m0s) stderrthreshold value logs at or above this threshold go to stderr (default 1) tablet_dir

data and provide a distributed locking service. Vitess uses a plug-in system to support various backends for storing topology data, which are assumed to provide a distributed, consistent key-value store Type Definition emit_stats boolean true iff we should emit stats to push-based monitoring/stats backends grpc_auth_mode string Which auth plugin implementation to use (eg: static) grpc_auth_mtls_allowed_substrings exported variables. stats_emit_period duration Interval between emitting stats to all registered backends (default 1m0s) stderrthreshold value logs at or above this threshold go to stderr (default 1) tablet_dir

data and provide a distributed locking service. Vitess uses a plug-in system to support various backends for storing topology data, which are assumed to provide a distributed, consistent key-value store chance of success. However, it’s acceptable for retries to happen internally, for example to multiple backends, in case only a subset of backend are not functional. TRANSIENT_ERROR 11 TRANSIENT_ERROR is used exponential backoff, should succeed. Clients should be able to successfully retry the query on the same backends. Examples of things that can trigger this error: 1. Query has been throttled 2. VtGate could have

data and provide a distributed locking service. Vitess uses a plug-in system to support various backends for storing topology data, which are assumed to provide a distributed, consistent key-value store chance of success. However, it’s acceptable for retries to happen internally, for example to multiple backends, in case only a subset of backend are not functional. TRANSIENT_ERROR 11 TRANSIENT_ERROR is used exponential backoff, should succeed. Clients should be able to successfully retry the query on the same backends. Examples of things that can trigger this error: 1. Query has been throttled 2. VtGate could have