-
Notifications
You must be signed in to change notification settings - Fork 3.7k
[debug](exchange) checks on both the sending and receiving sides of the exchange. #57346
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
Conversation
)" This reverts commit ac8b1b1.
|
run buildall |
HappenLee
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
|
PR approved by at least one committer and no changes requested. |
|
PR approved by anyone and no changes requested. |
|
run buildall |
TPC-DS: Total hot run time: 190355 ms |
ClickBench: Total hot run time: 27.85 s |
BE UT Coverage ReportIncrement line coverage Increment coverage report
|
BE Regression && UT Coverage ReportIncrement line coverage Increment coverage report
|
BE Regression && UT Coverage ReportIncrement line coverage Increment coverage report
|
1 similar comment
BE Regression && UT Coverage ReportIncrement line coverage Increment coverage report
|
…he exchange. (apache#57346) We've previously had sporadic core dumps. They can be clearly linked to the send_multi_blocks functionality. However, it's hard to reproduce when compiled with ASAN, so we've added some checking code here (because we suspect memory has already been corrupted). Please do not pick this into any release branches!!!
…des of the exchange." (apache#57740) Reverts apache#57346 We already know why the core issue is triggered—see the apache#57735 description for details. However, we want to fix the problem once and for all, so we'll complete the TODO items directly in a subsequent PR.
What problem does this PR solve?
We've previously had sporadic core dumps.
They can be clearly linked to the send_multi_blocks functionality.
However, it's hard to reproduce when compiled with ASAN, so we've added some checking code here (because we suspect memory has already been corrupted).
Please do not pick this into any release branches!!!
Release note
None
Check List (For Author)
Test
Behavior changed:
Does this need documentation?
Check List (For Reviewer who merge this PR)