Uh oh!
There was an error while loading. Please reload this page.
[fix](nereids)set RuntimeFilterInfo only on BE which is merge node - #57108
Conversation
hello-stephen
commented
Oct 17, 2025
Thank you for your contribution to Apache Doris. Please clearly describe your PR:
|
englefly
commented
Oct 20, 2025
run buildall |
doris-robot
commented
Oct 20, 2025
ClickBench: Total hot run time: 32.44 s |
hello-stephen
commented
Oct 20, 2025
FE UT Coverage ReportIncrement line coverage |
hello-stephen
commented
Oct 20, 2025
FE Regression Coverage ReportIncrement line coverage |
englefly
commented
Oct 21, 2025
run buildall |
doris-robot
commented
Oct 21, 2025
Cloud UT Coverage ReportIncrement line coverage Increment coverage report
|
hello-stephen
commented
Oct 21, 2025
FE UT Coverage ReportIncrement line coverage |
doris-robot
commented
Oct 21, 2025
TPC-DS: Total hot run time: 190659 ms |
doris-robot
commented
Oct 21, 2025
ClickBench: Total hot run time: 28.53 s |
doris-robot
commented
Oct 21, 2025
BE UT Coverage ReportIncrement line coverage Increment coverage report
|
hello-stephen
commented
Oct 21, 2025
BE Regression && UT Coverage ReportIncrement line coverage Increment coverage report
|
hello-stephen
commented
Oct 21, 2025
FE Regression Coverage ReportIncrement line coverage |
PR approved by at least one committer and no changes requested. |
PR approved by anyone and no changes requested. |
Uh oh!
There was an error while loading. Please reload this page.
…57108) set RuntimeFilterInfo only on BE which is merge node. note: RuntimeFilterInfo only contains runtime-filter merge information, not runtime filter descriptor In the previous pull request #56978, we moved the runtime info (which records how runtime filters are merged) from the instance level to the Backend (BE) level. In a multi-BE environment, when a runtime filter needs to be merged, the BE does not perform the merge using the mergeInstance specified by the Runtime Filter descriptor. Instead, it selects a BE that has the RuntimeInfo set to perform the merge. This causes BEs that should not be responsible for merging to wait for other nodes to send local runtime filters, resulting in a time
…pache#57108) set RuntimeFilterInfo only on BE which is merge node. note: RuntimeFilterInfo only contains runtime-filter merge information, not runtime filter descriptor In the previous pull request apache#56978, we moved the runtime info (which records how runtime filters are merged) from the instance level to the Backend (BE) level. In a multi-BE environment, when a runtime filter needs to be merged, the BE does not perform the merge using the mergeInstance specified by the Runtime Filter descriptor. Instead, it selects a BE that has the RuntimeInfo set to perform the merge. This causes BEs that should not be responsible for merging to wait for other nodes to send local runtime filters, resulting in a time
What problem does this PR solve?
set RuntimeFilterInfo only on BE which is merge node.
note: RuntimeFilterInfo only contains runtime-filter merge information, not runtime filter descriptor
In the previous pull request #56978, we moved the runtime info (which records how runtime filters are merged) from the instance level to the Backend (BE) level. In a multi-BE environment, when a runtime filter needs to be merged, the BE does not perform the merge using the mergeInstance specified by the Runtime Filter descriptor. Instead, it selects a BE that has the RuntimeInfo set to perform the merge. This causes BEs that should not be responsible for merging to wait for other nodes to send local runtime filters, resulting in a timeout.
Issue Number: close #xxx
Related PR: #xxx
Problem Summary:
Release note
None
Check List (For Author)
Test
Behavior changed:
Does this need documentation?
Check List (For Reviewer who merge this PR)