-
Notifications
You must be signed in to change notification settings - Fork 526
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
fix: clear shared buffer on stop_all_actors #3513
Conversation
Codecov Report
@@ Coverage Diff @@
## main #3513 +/- ##
==========================================
+ Coverage 74.41% 74.44% +0.03%
==========================================
Files 771 770 -1
Lines 108925 108509 -416
==========================================
- Hits 81052 80778 -274
+ Misses 27873 27731 -142
Flags with carried forward coverage won't be shown. Click here to find out more.
📣 Codecov can now indicate which changes are the most critical in Pull Requests. Learn more |
fffbcf0
to
fad15c8
Compare
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.
Rest LGTM.
Hey @hzxa21, this pull request failed to merge and has been dequeued from the merge train. If you believe your PR failed in the merge train because of a flaky test, requeue it by commenting with |
1d0940d
to
56c8d3d
Compare
* fix: clear shared buffer on stop_all_actors * Use a SharedBufferEvent to clear shared buffer and pending write requests * address comments
I hereby agree to the terms of the Singularity Data, Inc. Contributor License Agreement.
What's changed and what's your intention?
During the recovery process, we stop all actors in the compute node but we miss to clear buffers in storage, which keeps the memory unreleased. This PR fixes the problem by adding a method to clear shared buffer and calling it on stop_all_actors.
Checklist
./risedev check
(or alias,./risedev c
)Refer to a related PR or issue link (optional)