There are brief explanations in this slide (and next page).
https://www.slideshare.net/matsunobu/myrocks-deep-dive/120
After starting a new instance, in the error log, binlog position of the copy source instance is printed like this.
RocksDB: Last binlog file position 60819992, file name binary-logs.000001
So if you find associated GTID set from the binlog file/position, you can start replication. Finding GITD set can be done
by executing “SHOW GTID EXECUTED IN ‘$binlog_file’ FROM $binlog_pos;” on the copy source instance.
After getting GTID, you can start replication by SET GLOBAL GTID_PURGED=’$gtid_set’; CHANGE MASTER…
(https://www.slideshare.net/matsunobu/myrocks-deep-dive/121 has some details).
--
You received this message because you are subscribed to the Google Groups "MyRocks - RocksDB storage engine for MySQL" group.
To unsubscribe from this group and stop receiving emails from it, send an email to
myrocks-dev...@googlegroups.com.
To post to this group, send email to
myroc...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/myrocks-dev/1f20bb77-92b0-45bd-ad6e-ebbc882d041c%40googlegroups.com.
For more options, visit
https://groups.google.com/d/optout.