Fix flaky tests with distributed queries

There was few attempts to fix this [1] and [2], but it still pops up
sometimes, for example here [3].

  [1]: 009f57fc2f / #11211
  [2]: cdb6bed8b9 / #14198
  [3]: https://clickhouse-test-reports.s3.yandex.net/21318/38be9ff43ac4c46ce6e803fc125d910bde1d4c71/functional_stateless_tests_(release,_databasereplicated).html#fail1

Let's use more generic approach, and do not hide any errors (and see
does increasing timeout will be enough).
This commit is contained in:
Azat Khuzhin 2021-03-03 23:32:53 +03:00
parent 9244bc43ee
commit 7794ac66d4
6 changed files with 12 additions and 14 deletions

View File

@ -39,6 +39,7 @@ ln -sf $SRC_PATH/users.d/readonly.xml $DEST_SERVER_PATH/users.d/
ln -sf $SRC_PATH/users.d/access_management.xml $DEST_SERVER_PATH/users.d/
ln -sf $SRC_PATH/users.d/database_atomic_drop_detach_sync.xml $DEST_SERVER_PATH/users.d/
ln -sf $SRC_PATH/users.d/opentelemetry.xml $DEST_SERVER_PATH/users.d/
ln -sf $SRC_PATH/users.d/remote_queries.xml $DEST_SERVER_PATH/users.d/
ln -sf $SRC_PATH/ints_dictionary.xml $DEST_SERVER_PATH/
ln -sf $SRC_PATH/strings_dictionary.xml $DEST_SERVER_PATH/

View File

@ -0,0 +1,9 @@
<yandex>
<profiles>
<default>
<!-- Avoid "Connection failed at try №1" messages. -->
<connect_timeout_with_failover_ms>2000</connect_timeout_with_failover_ms>
<connect_timeout_with_failover_secure_ms>3000</connect_timeout_with_failover_secure_ms>
</default>
</profiles>
</yandex>

View File

@ -1,7 +1,3 @@
-- Avoid "Connection failed at try №1" messages.
SET send_logs_level = 'none';
SET connect_timeout_with_failover_ms = 5000;
DROP TABLE IF EXISTS source_table1;
DROP TABLE IF EXISTS source_table2;
DROP TABLE IF EXISTS distributed_table1;

View File

@ -1,9 +1,5 @@
-- TODO: correct testing with real unique shards
-- Avoid "Connection failed at try №1" messages.
SET send_logs_level = 'fatal';
SET connect_timeout_with_failover_ms = 5000;
set optimize_distributed_group_by_sharding_key=1;
drop table if exists dist_01247;

View File

@ -1,9 +1,5 @@
-- TODO: correct testing with real unique shards
-- Avoid "Connection failed at try №1" messages.
SET send_logs_level = 'fatal';
SET connect_timeout_with_failover_ms = 5000;
set optimize_distributed_group_by_sharding_key=1;
drop table if exists dist_01247;

View File

@ -1,5 +1,5 @@
send_timeout Seconds 300
connect_timeout Seconds 10
connect_timeout_with_failover_ms Milliseconds 50
connect_timeout_with_failover_secure_ms Milliseconds 100
connect_timeout_with_failover_ms Milliseconds 2000
connect_timeout_with_failover_secure_ms Milliseconds 3000
max_memory_usage UInt64 10000000000