[MDEV-7114] Online DDL does not behave like expected Created: 2014-11-14 Updated: 2014-11-21 Resolved: 2014-11-21 |
|
| Status: | Closed |
| Project: | MariaDB Server |
| Component/s: | Replication, Storage Engine - InnoDB |
| Affects Version/s: | 10.0.14 |
| Fix Version/s: | 10.0.15 |
| Type: | Bug | Priority: | Major |
| Reporter: | VAROQUI Stephane | Assignee: | Sergei Golubchik |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | upstream-fixed | ||
| Issue Links: |
|
||||||||
| Description |
|
We are using regular replication no GTID on master -> slaves setup Running on the master
We observe :
optimize table pages;
|
| Comments |
| Comment by VAROQUI Stephane [ 2014-11-14 ] |
|
Upstream related issue Bug #18734396, Bug #72594 |
| Comment by Elena Stepanova [ 2014-11-14 ] |
|
Since the fix is in InnoDB 5.6.21, it should appear in 10.0.15 along with the InnoDB/XtraDB merge. |
| Comment by VAROQUI Stephane [ 2014-11-14 ] |
|
I guess that upstream fixe the corruption , but it those not say anythings about alter online is not replication friendly so not really ONLINE at the end. Should alter online table be fast and free the connection and move the alter in a background THD or is that expected to wait on the client until it's finished ? On my experience ALTER ONLINE on toku is a background task. That's not what i observe in xtradb with the above DDL. Using GTID design, by changing domain id we possibly can fixe the replication delay, moving the online task to an other replication THD. Is that needed or Online should not blocked by definition ? |
| Comment by Sergei Golubchik [ 2014-11-21 ] |
|
InnoDB/XtraDB 5.6.21 is merged |