Randomize some settings in functional tests

[Avogar]

Changelog category (leave one):

• Build/Testing/Packaging Improvement

Changelog entry (a user-readable short description of the changes that goes to CHANGELOG.md):
Randomize some settings in functional tests. This closes #32268.

[alexey-milovidov]

optimize_move_to_prewhere = 0|1

[alexey-milovidov]

prefer_localhost_replica = 0|1

[alexey-milovidov]

group_by_two_level_threshold
group_by_two_level_threshold_bytes

With 10% probability set to very low value (to activate always) and with 10% set to very high value (to never activate)

[alexey-milovidov]

distributed_aggregation_memory_efficient = 0|1

[alexey-milovidov]

allow_experimental_parallel_reading_from_replicas = 0|1

[alexey-milovidov]

max_insert_threads with probability 1/2 set it uniformly random 1..16

[alexey-milovidov]

output_format_parallel_formatting = 0|1

[alexey-milovidov]

PS. We can adapt existing tests then add more randomization in subsequent PR.

[alexey-milovidov]

@den-crane @SaltTan Maybe you can recall some problematic settings from your experience.

[tavplubix]

We should print changed settings somewhere in logs to simplify debugging

[Algunenano]

Love the idea but do you really want to introduce them all at once? The last similar thing done was to run under a random timezone and it took weeks and many PRs to stabilize things.

[alexey-milovidov]

I'm ok if it will take weeks.

[Avogar]

@Mergifyio update

[mergify]

update

✅ Branch has been successfully updated

[SaltTan]

@den-crane @SaltTan Maybe you can recall some problematic settings from your experience.

I'm sorry it took me so long.

• optimize*
• enable*
• use*
• compile_aggregate_expressions
• compile_expressions
• There was an issue with 'read_backoff' once.

[Avogar]

@Mergifyio update

[mergify]

update

✅ Branch has been successfully updated