Not follow rotate event & no interested event may cause data loss

zzt93 / syncer

Sync & Manipulate data from MySQL/MongoDB to Elasticsearch/MySQL/Kafka Endpoint

BSD 3-Clause "New" or "Revised" License

69 stars 29 forks source link

Not follow rotate event & no interested event may cause data loss #4

Closed zzt93 closed 6 years ago

zzt93 commented 6 years ago

Precondtion: Not follow rotate event & no interested event for a specific consumer

Next: This consumer will not update binlog position to follo. If the syncer stopped, then some interested event is added and old binlog is removed. We may just connect to latest binlog position and lost some data.

Solution: listen to rotate event.

zzt93 commented 6 years ago

Fixed in this commit in branch pressureTest