Skip to content
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

ALTER TABLE ENGINE=InnoDB does not work #17

Open
philip-galera opened this issue Nov 19, 2014 · 0 comments
Open

ALTER TABLE ENGINE=InnoDB does not work #17

philip-galera opened this issue Nov 19, 2014 · 0 comments
Labels

Comments

@philip-galera
Copy link
Contributor

ALTER TABLE ENIGINE=InnoDB from MyISAM does not work with Galera. As the original table was never replicated on the slaves, the ALTER on the slaves operates on an empty MyISAM table and produces an empty InnoDB table. Further queries against that table cause the slave applier to fail.

The workaround suggested by Jay is to enable MyISAM replication as well, however this does not help much with MyISAM tables that have been created previously.

I guess the fix would be intercept the InnoDB writes that the ALTER statement produces and replicate them.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants