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 author connections. Vitess creates very lightweight connections. Vitess’ connection pooling feature uses Go’s concurrency support to map these lightweight connections to a small pool of MySQL connections. As such, Vitess multi-master configurations), or performance related features (locking that table’s current ID may have concurrency implications). • When inserting a row in a table with an auto-increment column, if the value for

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 181 Concurrency . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 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 author connections. Vitess creates very lightweight connections. Vitess’ connection pooling feature uses Go’s concurrency support to map these lightweight connections to a small pool of MySQL connections. As such, Vitess

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 look over connections. Vitess creates very lightweight connections. Vitess’ connection pooling feature uses Go’s concurrency support to map these lightweight connections to a small pool of MySQL connections. As such, Vitess multi-master configurations), or performance related features (locking that table’s current ID may have concurrency implications). • When inserting a row in a table with an auto-increment column, if the value for

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 author connections. Vitess creates very lightweight connections. Vitess’ connection pooling feature uses Go’s concurrency support to map these lightweight connections to a small pool of MySQL connections. As such, Vitess multi-master configurations), or performance related features (locking that table’s current ID may have concurrency implications). • When inserting a row in a table with an auto-increment column, if the value for

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 look over connections. Vitess creates very lightweight connections. Vitess’ connection pooling feature uses Go’s concurrency support to map these lightweight connections to a small pool of MySQL connections. As such, Vitess multi-master configurations), or performance related features (locking that table’s current ID may have concurrency implications). • When inserting a row in a table with an auto-increment column, if the value for

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 look over connections. Vitess creates very lightweight connections. Vitess’ connection pooling feature uses Go’s concurrency support to map these lightweight connections to a small pool of MySQL connections. As such, Vitess multi-master configurations), or performance related features (locking that table’s current ID may have concurrency implications). • When inserting a row in a table with an auto-increment column, if the value for

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 look over connections. Vitess creates very lightweight connections. Vitess’ connection pooling feature uses Go’s concurrency support to map these lightweight connections to a small pool of MySQL connections. As such, Vitess multi-master configurations), or performance related features (locking that table’s current ID may have concurrency implications). • When inserting a row in a table with an auto-increment column, if the value for

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 look over connections. Vitess creates very lightweight connections. Vitess’ connection pooling feature uses Go’s concurrency support to map these lightweight connections to a small pool of MySQL connections. As such, Vitess connection pool running out of connections is not necessarily a bad thing, since it limits the concurrency in the database. As a result, connection pools should be sized mindful of the capacity of the underlying

topoReadPool.Release() if err != nil { return nil, err } var ( m sync.Mutex wg sync.WaitGroup rec concurrency.AllErrorRecorder keyspaces = make([]*vtadminpb.Keyspace, len(resp.Keyspaces)) ) for i, ks :=