4

Get trx position when inconsistent backup is taken · Issue #678 · mydumper/mydum...

 1 year ago
source link: https://github.com/mydumper/mydumper/issues/678
Go to the source link to view the article. You can view the picture content, updated content and better typesetting reading experience. If the link is broken, please click the button below to view the snapshot at that time.

Member

davidducos commented on May 12

In order to avoid FTWRL, we could start the threads and check the trx position that they are seeing:
For instance, after executing start transaction with consistent snapshot:

---TRANSACTION 30883, ACTIVE 100 sec
3 lock struct(s), heap size 1128, 1 row lock(s), undo log entries 1
MySQL thread id 43646, OS thread handle 139897893787392, query id 760645 172.28.128.70 root starting
show engine innodb status
Trx read view will not see trx with id >= 30883, sees < 30883

We can check at what trx id is each mydumper thread and determine if all are in the same position as they will be if FTWRL were executed.

report

Recommend

About Joyk


Aggregate valuable and interesting links.
Joyk means Joy of geeK