ClickHouse/tests/config/users.d/remote_queries.xml

<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>
            <!-- Avoid this logic in tests to avoid EOF (10 hours is enough for tests)-->
            <idle_connection_timeout>36000</idle_connection_timeout>
            <!-- NOTE: instead of tunning idle_connection_timeout,
                 SYSTEM RELOAD CONFIG can be executed before each test -->
        </default>
    </profiles>
</yandex>
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]: 009f57fc2fc8 / #11211 [2]: cdb6bed8b98e / #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). 2021-03-03 20:32:53 +00:00			`<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>`
Tune idle_connection_timeout to avoid reconnects There may be 1 hour between two different distributed queries in tests (see [1] and [2]), if this will happen then the connection may be closed already due to idle_connection_timeout. [1]: https://clickhouse-test-reports.s3.yandex.net/21432/572d5862961ffda88125679e3a5ea684c316b223/functional_stateless_tests_(debug).html#fail1 [2]: https://clickhouse-test-reports.s3.yandex.net/21432/572d5862961ffda88125679e3a5ea684c316b223/functional_stateless_tests_(antlr_debug).html#fail1 Let's tune it to avoid such issues and override other settings in tests. Another option is to execute SYSTEM RELOAD CONFIG before each test... 2021-03-04 19:48:09 +00:00			`<!-- Avoid this logic in tests to avoid EOF (10 hours is enough for tests)-->`
			`<idle_connection_timeout>36000</idle_connection_timeout>`
			`<!-- NOTE: instead of tunning idle_connection_timeout,`
			`SYSTEM RELOAD CONFIG can be executed before each test -->`
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]: 009f57fc2fc8 / #11211 [2]: cdb6bed8b98e / #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). 2021-03-03 20:32:53 +00:00			`</default>`
			`</profiles>`
			`</yandex>`