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

2PC should be supported during resharding cutover #5108

Closed
sougou opened this issue Aug 17, 2019 · 1 comment
Closed

2PC should be supported during resharding cutover #5108

sougou opened this issue Aug 17, 2019 · 1 comment
Labels
Component: Query Serving Component: VReplication Type: Enhancement Logical improvement (somewhere between a bug and feature)

Comments

@sougou
Copy link
Contributor

sougou commented Aug 17, 2019

2PC transactions currently don't work when writes are migrated during resharding. The challenge is that the redo logs contain original statements, which cannot be routed to the correct shard through vreplication that relies on RBR.

One possible short-term solution will be to disable 2PC during a resharding cutover. The cutover process can disable 2PC in the source shards, and re-enable them after the writes are migrated.

Longer term: we should look at relying on the XA API of the newer mysqls. For this, we have to validate that the behavior is as expected for all corner cases: replication, semi-sync, crash recovery, etc.

@morgo morgo added the Type: Enhancement Logical improvement (somewhere between a bug and feature) label Oct 28, 2019
@mattlord
Copy link
Contributor

I'm closing this as superseded by #16245

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Component: Query Serving Component: VReplication Type: Enhancement Logical improvement (somewhere between a bug and feature)
Projects
None yet
Development

No branches or pull requests

4 participants