-
Notifications
You must be signed in to change notification settings - Fork 322
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: thread races in aggregator if there are concurrent Put
s
#2472
fix: thread races in aggregator if there are concurrent Put
s
#2472
Conversation
Codecov ReportBase: 35.89% // Head: 75.82% // Increases project coverage by
Additional details and impacted files@@ Coverage Diff @@
## main #2472 +/- ##
=============================================
+ Coverage 35.89% 75.82% +39.93%
- Complexity 368 371 +3
=============================================
Files 154 638 +484
Lines 9007 120084 +111077
Branches 1056 1058 +2
=============================================
+ Hits 3233 91053 +87820
- Misses 5558 28814 +23256
- Partials 216 217 +1
Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here. ☔ View full report at Codecov. |
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
What kind of change does this PR introduce? (Bug fix, feature, docs update, ...)
Fix Failed to import data with longwindow in online sever #2465
What is the current behavior? (You can also link to an open issue here)
The binlog_offset may be out-of-order to the aggregator if there are concurrent
Put
s.However
aggregator
assumes it is strictly in order.What is the new behavior (if this is a feature change)?
Aggregator update
is protected bybinlog mutex
and is called as a closure parameter inside binlog.This is a quick fix. A better solution will be doing asynchronous update to the aggregators from the binlog.