-
Notifications
You must be signed in to change notification settings - Fork 33
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Multi-table OPTIMIZE, REPAIR leads to BF-BF conflict, node abort #198
Comments
What was the conclusion from our prior discussion? Is OPTIMIZE TABLES binlogged? Do we even want to replicate it? |
Optimize table is binlogged, so should be replicated. |
Test case:
|
REPAIR TABLE is also affected, using the same test case as above, but the assertion is different:
|
ANALYZE, CHECK, CHECKSUM TABLE do not seem to be affected (though I guess it is best to confirm this by code inspection). DROP TABLE, RENAME TABLE, DROP VIEW do not seem to be affected. The DML reports that the table is no longer there. |
We just got the same issue:
our database version is: Percona-XtraDB-Cluster-56 version 5.6.24-25.11.1.el7; it's a 2 mysqld node + garbd cluster setup. |
@mmpower . You will need to disable the Broken Link Checker WordPress plugin until this is fixed. Alternatively you can edit the source of the plugin to not perform multi-table OPTIMIZE TABLEs. |
thanks @philip-galera . we just tested the newer percona xtradb version seems it does not happen any more....seem it's already fixed in percona release https://www.percona.com/doc/percona-xtradb-cluster/5.6/release-notes/Percona-XtraDB-Cluster-5.6.25-25.12.html? |
Possibly related commit in PXC tree: percona/percona-xtradb-cluster@5065122 |
* Total order isolation was started twice for FLUSH TABLES, from reload_acl_and_cache() and from mysql_execute_command(). Removed the reload_acl_and_cache() part. * Removed PXC specific stuff from MTR tests
Restore tests for FLUSH commands supported by MariaDB.
MW-362 RESET MASTER is not allowed if wsrep is enabled.
With multi-table OPTIMIZE TABLE:
Teemu says:
The text was updated successfully, but these errors were encountered: