-
Notifications
You must be signed in to change notification settings - Fork 289
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
cdc: update position and status as soon as possible #481
Conversation
/run-integration-tests |
1 similar comment
/run-integration-tests |
8aa6a41
to
ad00ac5
Compare
/run-integration-tests |
2f1348c
to
b8eeb2e
Compare
/run-integration-tests |
b8eeb2e
to
9219358
Compare
/run-integration-tests |
9219358
to
e94a27e
Compare
/run-integration-tests |
/run-integration-tests |
2237237
to
40fd98f
Compare
/run-integration-tests |
3 similar comments
/run-integration-tests |
/run-integration-tests |
/run-integration-tests |
c8163cc
to
0449660
Compare
/run-integration-tests |
0449660
to
1ccbf9e
Compare
/run-integration-tests |
1ccbf9e
to
978b1dc
Compare
/run-integration-tests |
1 similar comment
/run-integration-tests |
Codecov Report
@@ Coverage Diff @@
## master #481 +/- ##
================================================
- Coverage 31.4302% 31.0645% -0.3657%
================================================
Files 70 70
Lines 6831 6876 +45
================================================
- Hits 2147 2136 -11
- Misses 4525 4580 +55
- Partials 159 160 +1 |
5c1150b
to
eab6cd8
Compare
/run-integration-tests |
/run-kafka-tests |
…d-owner # Conflicts: # cdc/changefeed.go # cdc/processor.go
/run-integration-tests |
…d-owner # Conflicts: # cdc/changefeed.go # cdc/processor.go
/run-integration-tests |
/run-integration-tests |
/run-integration-tests |
/run-integration-tests |
1 similar comment
/run-integration-tests |
/run-integration-tests |
/run-all-tests |
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
/run-all-tests |
What problem does this PR solve?
Resolve #468.
What is changed and how it works?
For
processor
do a tiny refactor to wakeup it when the resolved ts or status have changed.For
owner
it is hard to refactor the main loop, so I just add a side-channel to process an updated position as soon as possible.We can improve the efficiency of the current event model in some harder ways, such as reduce the etcd queries, do less work in the event loop, redesign the whole interaction model, etc. But these ways will change a lot of code and introduce new bugs.
For now, it is safer to do some little changes like this PR to gain some performance improvements in some scenarios.
Check List
Simple benchmark pingcap/ticdc#481 (comment)
Release note
Tests