often fails due to MySQL unable to start with following error:
Note that RocksDB engine needs to be enabled, otherwise MySQL starts successfully.
Test bug1254227.sh doesn't fail, mysql rolls back XA transaction on startup.
xtrabackup is missing following patch which used to rollback XA transactions in previous versions:
If we put that patch back everything becomes OK with InnoDB. This however needs to be tested with transactions involving both RocksDB and InnoDB.
Also, considering out approach to RocksDB backup we won't be able to rollback prepared XA transactions in RocksDB. Workaround I have found for rocksdb is to copy MySQL binary log to the backup directory.
Test case:
often fails due to MySQL unable to start with following error:
Note that RocksDB engine needs to be enabled, otherwise MySQL starts successfully.
Test bug1254227.sh doesn't fail, mysql rolls back XA transaction on startup.
xtrabackup is missing following patch which used to rollback XA transactions in previous versions:
If we put that patch back everything becomes OK with InnoDB. This however needs to be tested with transactions involving both RocksDB and InnoDB.
Also, considering out approach to RocksDB backup we won't be able to rollback prepared XA transactions in RocksDB. Workaround I have found for rocksdb is to copy MySQL binary log to the backup directory.