[MDEV-630] LP:917129 - Replication failure on concurrent REMOVE PARTITIONING and OPTIMIZE PARTITION Created: 2012-01-16 Updated: 2023-11-28 |
|
| Status: | Open |
| Project: | MariaDB Server |
| Component/s: | Replication |
| Affects Version/s: | 5.5.28, 5.5, 10.0, 10.1, 10.2, 10.4, 10.5, 10.6, 10.10, 10.11, 11.0, 11.1 |
| Fix Version/s: | 10.4, 10.5, 10.6, 10.11, 11.0, 11.1 |
| Type: | Bug | Priority: | Minor |
| Reporter: | Elena Stepanova | Assignee: | Nikita Malyavin |
| Resolution: | Unresolved | Votes: | 0 |
| Labels: | Launchpad, upstream-fixed | ||
| Attachments: |
|
| Description |
|
In the provided test case, REMOVE PARTITIONING is run in parallel with OPTIMIZE PARTITION. On master, OPTIMIZE partition starts first and doesn't cause an error, but in the binary log it is written after REMOVE PARTITIONING, and it makes SQL slave thread abort with ER_PARTITION_MGMT_ON_NONPARTITIONED. It's only reproducible with InnoDB tables, so it might be related to optimize not being supported and executed as recreate + analyze instead:
Affects 5.1, 5.2, 5.3, 5.5. Also reproducible on MySQL 5.1.60, 5.5.20, 5.6.4 and filed as http://bugs.mysql.com/bug.php?id=64041.
|
| Comments |
| Comment by Rasmus Johansson (Inactive) [ 2012-03-29 ] |
|
Launchpad bug id: 917129 |
| Comment by Elena Stepanova [ 2017-11-22 ] |
|
Still reproducible on 5.5-10.3, MySQL 5.5. |