Skip to content

GTID replication pointer issue #132

Open
@srakhmanchuk

Description

@srakhmanchuk

Hi! I’ve noticed unexpected behavior when relying on GTID as a replication pointer.

Assume MySQL has executed the following transactions:

b1988e6b-e20e-11ee-916d-0242ac350008:1
b1988e6b-e20e-11ee-916d-0242ac350008:2
b1988e6b-e20e-11ee-916d-0242ac350008:3
b1988e6b-e20e-11ee-916d-0242ac350008:4
...
b1988e6b-e20e-11ee-916d-0242ac350008:300

Upon connection, the script informs the master node that the latest processed transaction is: b1988e6b-e20e-11ee-916d-0242ac350008:300. However, for some reason, MySQL continues to send past transactions (1,2,3,4 ... ), leading to event data duplication.

What could be causing this issue?

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions