Files
datastore/tests/config/config.d/background_schedule_pool_log.yaml
Azat Khuzhin fcc187cf54 Increase background_schedule_pool_log.duration_threshold_milliseconds
Otherwise it is too much, one job in CI:
- text_log: 4'500'000
- zookeeper_log: 6'400'000
- background_schedule_pool_log: 54'000'000
- background_schedule_pool_log where duration_ms > 0: 19'400

But this is CI real values are different [1], so let's use average task
executiong time for threshold.

  [1]: https://pastila.nl/?0043db0f/96b45f5ddb995fb78c11d301d7a49f27#foCK+BCRTTH/kLTqvZ7G8g==

It should resolve flakiness due to TOO_MANY_ROWS [2].

  [2]: https://s3.amazonaws.com/clickhouse-test-reports/json.html?REF=master&sha=f7b1a4850b1597b443b472adbf0e2cd4f5a3b0bd&name_0=MasterCI&name_1=Stateless%20tests%20%28amd_binary%2C%20old%20analyzer%2C%20s3%20storage%2C%20DatabaseReplicated%2C%20parallel%29&name_1=Stateless%20tests%20%28amd_binary%2C%20old%20analyzer%2C%20s3%20storage%2C%20DatabaseReplicated%2C%20parallel%29
2025-12-24 12:30:41 +01:00

4 lines
120 B
YAML

background_schedule_pool_log:
# duration > 0 will still filter enough for CI
duration_threshold_milliseconds: 1