I saw the following in the logs for the failed test:
2023.05.16 07:12:12.894051 [ 262 ] {74575ac0-b296-4fdc-bc8e-3476a305e6ea} <Warning> ConnectionPoolWithFailover: Connection failed at try №1, reason: Timeout exceeded while reading from socket (socket (172.16.3.2:9000), receive timeout 2000 ms)
And I think that the culprit is the
test_distributed_replica_max_ignored_errors for which it is normal,
however not for others, and this should not affect other tests.
So fix this by calling SYSTEM RELOAD CONFIG, which should reset error
count.
CI: https://s3.amazonaws.com/clickhouse-test-reports/49380/5abc1a1c68ee204c9024493be1d19835cf5630f7/integration_tests__release__[3_4].html
Signed-off-by: Azat Khuzhin <a.khuzhin@semrush.com>
This PR formats all the `*.py` files found under the `tests/integration`
folder. It also reorders the imports and cleans up a bunch of unused
imports.
The formatting also takes care of other things like wrapping lines and
fixing spaces and indents such that the tests look more readable.
At startup, server loads configuration files.
However ConfigReloader does not know about already loaded files (files
is empty()), hence it will always reload the configuration just after
server starts (+ 2 seconds, reload timeout).
And on configuration reload the clusters will be re-created, so some
internal stuff will be reseted:
- error_count
- last_used (round_robing)
And if the reload will happen during round_robin test it will start
querying from the beginning, so let's issue config reload just after
start to avoid reload in the middle of the test execution.
