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

Question: Does vitess support XA transaction? #16571

Closed
jan-brinkmann opened this issue Aug 9, 2024 · 4 comments
Closed

Question: Does vitess support XA transaction? #16571

jan-brinkmann opened this issue Aug 9, 2024 · 4 comments

Comments

@jan-brinkmann
Copy link

Question

As stated in the title, does vitess support XA transactions as a special case of 2PC?

I found a nine year old issue on that, where XA transaction is announced: #536
However, I do not find XA transaction in the documentation.

@jan-brinkmann jan-brinkmann added Needs Triage This issue needs to be correctly labelled and triaged Type: Question labels Aug 9, 2024
@harshit-gangal
Copy link
Member

Hi @jan-brinkmann
We are working on adding support for atomic cross-shard transactions.
It should not impact what we use under the hood, whether it is XA protocol or Vitess's implementation.

For the user, to enable the atomic cross-shard transactions, they should set the transaction mode to 2PC via set transaction_mode = twopc and then any transaction that goes cross-shard will be atomically committed.

We will be updating the existing doc on TWOPC with updated information once the feature is ready for use.

@harshit-gangal harshit-gangal added Component: Query Serving and removed Needs Triage This issue needs to be correctly labelled and triaged labels Aug 9, 2024
@harshit-gangal
Copy link
Member

You can follow along the work with open RFC: #16245

@jan-brinkmann
Copy link
Author

@harshit-gangal, thank you! 😊

@GuptaManan100
Copy link
Member

GuptaManan100 commented Aug 28, 2024

The question seems to have been answered and the RFC for the support is open and being worked on. I'm going to close this issue, please open a new one if there are any other questions/issues.

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

No branches or pull requests

3 participants