Skip to content
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: do not use gtid if gtid is disabled #1781

Merged
merged 1 commit into from
Sep 25, 2024

Conversation

yyuuttaaoo
Copy link
Collaborator

Fixed an issue where the input_canal plugin used GTID as the sync method even when gtid_enabled was set to false. This led to syncing from the beginning due to receiving an empty GTID set. Syncing from the beginning is usually undesirable as it consumes significant CPU resources on the server side and deviates from the default plugin behavior. This commit ensures that the plugin respects the gtid_enabled switch and the gtid_mode query result.

@yyuuttaaoo yyuuttaaoo added the bug Something isn't working label Sep 25, 2024
@yyuuttaaoo yyuuttaaoo added this to the v2.1 milestone Sep 25, 2024
@yyuuttaaoo yyuuttaaoo merged commit 5862d33 into alibaba:main Sep 25, 2024
14 of 15 checks passed
@yyuuttaaoo yyuuttaaoo deleted the fix/gtid_not_enabled branch September 25, 2024 02:08
yyuuttaaoo added a commit that referenced this pull request Sep 25, 2024
Fixed an issue where the input_canal plugin used GTID as the sync method even when gtid_enabled was set to false. This led to syncing from the beginning due to receiving an empty GTID set. Syncing from the beginning is usually undesirable as it consumes significant CPU resources on the server side and deviates from the default plugin behavior. This commit ensures that the plugin respects the gtid_enabled switch and the gtid_mode query result.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants