New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add a setting max_execution_time_leaf to limit the execution time on shard for distributed query #51823
Add a setting max_execution_time_leaf to limit the execution time on shard for distributed query #51823
Conversation
@alexey-milovidov @ucasfl can we consider adding this settings? I think it's also reasonable to have this settings when we only want to limit the execution time on remote shard, not on coordinator. |
This is an automated comment for commit dd6b02a with description of existing statuses. It's updated for the latest CI running ❌ Click here to open a full report in a separate page Successful checks
|
Sorry, we forgot about this pull request - we will pick it up. |
@canhld94 I've resolved conflicts and fixed typos, but more changes are needed. |
Signed-off-by: Duc Canh Le <duccanh.le@ahrefs.com>
Signed-off-by: Duc Canh Le <duccanh.le@ahrefs.com>
Signed-off-by: Duc Canh Le <duccanh.le@ahrefs.com>
Failed tests were related. It breaks test |
Changelog category (leave one):
Changelog entry (a user-readable short description of the changes that goes to CHANGELOG.md):
Add a setting
max_execution_time_leaf
to limit the execution time on shard for distributed query, andtimeout_overflow_mode_leaf
to control the behaviour if timeout happens.Close #46102
Documentation entry for user-facing changes