-
Notifications
You must be signed in to change notification settings - Fork 167
[#2674] improvement(client): use ack val to check the block send result #2703
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
base: master
Are you sure you want to change the base?
Conversation
jerqi
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.
|
Should Spark2 client be consistent with Spark3 client? |
Done.Merge the changes from #1179 |
zuston
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.
+1
|
|
||
| long currentAckValue = 0; | ||
| for (Long blockId : blockIds) { | ||
| currentAckValue ^= blockId; |
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.
lightweight and effective!
What changes were proposed in this pull request?
Use ack val to check the block send result.
Why are the changes needed?
For better performance.
Fix: #2674
Does this PR introduce any user-facing change?
No.
How was this patch tested?
CI