This is a known problem in general. There is an open ticket in sbroad:
https://git.picodata.io/picodata/picodata/sbroad/-/issues/542

This is a follow up for 8a2b10e2

Make it possible to pass enabled injections at process startup via env
variables.

If initial call to vshard.router.bootstrap failed with taimeout then
following calls return cluster already bootstrapped error. Make
proc_sharding_bootstrap treat this error as successful bootstrap.

Close: https://git.picodata.io/picodata/picodata/picodata/-/issues/751

If it's set only the "rows" part of the response is returned.
This parameter is True by default because in most cases this is what we
want.

Close #765

Arseniy Volynets authored 8 months ago and Dmitry Rodionov committed 8 months ago

- Some sql queries that read from sharded tables
can fail with timeout error, but because of rethrows
it is showed as 'Connection reset error'. In order
to avoid retrying such tests in CI we can use retries
in tests. Note: solution to the problem itself is in
the progress, but we don't know when it will be done:
https://github.com/tarantool/vshard/pull/442

- Another solution is to use global tables instead of
sharded tables in tests where it does not matter.

- This commit uses both approaches: when possible sharded
tables were replaced with global ones. In other cases retries
were used.