Issues with replication from 5.5 node to 5.6 node
Bug #1267494 reported by
Seppo Jaakola
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | ||
---|---|---|---|---|---|---|
MySQL patches by Codership |
Fix Released
|
High
|
Seppo Jaakola | |||
Percona XtraDB Cluster moved to https://jira.percona.com/projects/PXC | Status tracked in 5.6 | |||||
5.5 |
Invalid
|
Undecided
|
Unassigned | |||
5.6 |
Fix Released
|
Undecided
|
Unassigned |
Bug Description
This bug tracks issues with replication from 5.5 node to 5.6 node. There is a separate bug with replication in opposite direction: https:/
Replication direction 5.5-> 5.6 is critical, as it will be needed with online migration to 5.6 cluster
Changed in codership-mysql: | |
status: | New → In Progress |
importance: | Undecided → High |
assignee: | nobody → Seppo Jaakola (seppo-jaakola) |
milestone: | none → 5.6.15-25.2 |
description: | updated |
Changed in codership-mysql: | |
status: | Fix Committed → Fix Released |
To post a comment you must log in.
For migration to 5.6 cluster, we can assume that all 5.5 nodes will be upgraded first to use Galera replication 3.*, so that all nodes in the new cluster will run same Galera plugin version.
When testing such 5.5 -> 5.6 scenario, it turned out that parallel applying could hit a unresolvable conflict. But, after merging the fix for: https:/ /bugs.launchpad .net/codership- mysql/+ bug/1262887 , 5.5 -> 5.6 replication can run with several slave appliers in 5.6 node.
ATM, I see no issues with replication in this direction, will run more complex load still to verify.