-
Notifications
You must be signed in to change notification settings - Fork 188
syncer: update active relay log at fake rotate event #1448
Conversation
be2e7af
to
6934fc2
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.
The integration test name only_dml is confusing. Personally suggest changing to purge_relay_active or something else.
Rest LGTM.
this test aims covering a use case of only synchronizing dml, which is specified in release testing doc. |
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
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
Signed-off-by: ti-srebot <ti-srebot@pingcap.com>
cherry pick to release-2.0 in PR #1468 |
What problem does this PR solve?
in #1393, we support only specify GTID with no binlog filename, so we can't update active relay log filename at init time. Although active relay log will be updated when after
checkpoint-flush-interval
seconds and receiving an event, for the firstcheckpoint-flush-interval
seconds, purge-relay will fail because of no active relay log, which may confuse user.What is changed and how it works?
when only specify GTID with no binlog filename, use fake rotate event to update active relay log.
also, add a integration test to make sure active relay log is forwarded when there's only DML
Check List
Tests
Code changes
Side effects
Related changes