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

Associate arbitrary number of writesets with a single transaction ID #104

Open
ayurchen opened this issue Sep 2, 2014 · 0 comments
Open

Comments

@ayurchen
Copy link
Member

ayurchen commented Sep 2, 2014

This is needed for transaction fragmentation support. As it is now, transaction handle can hold only one writeset

@ayurchen ayurchen self-assigned this Sep 2, 2014
janlindstrom pushed a commit to MariaDB/galera that referenced this issue Oct 13, 2018
This commit

* introduces support for several fragments per TrxHandle
* does away with support for old, pre 3.x writeset format
* introduces storing of IST writesets in GCache
* breaks TrxHandle into local and remote variants, each with own FSM
janlindstrom pushed a commit to MariaDB/galera that referenced this issue Oct 13, 2018
- fixed canceling commit monitor in case of streaming trx
- fixed REPLICATING->EXECUTING transition
- typos fixes in wsrep_api.h
janlindstrom pushed a commit to MariaDB/galera that referenced this issue Oct 13, 2018
- removed no longer used members from TrxHandle classes
- switched from std::vector to gu::Vector to avoid extra heap allocation during TrxHandeMaster construction
- added push_back(), front() and back() methods to gu::Vector
- further code cleanups
janlindstrom pushed a commit to MariaDB/galera that referenced this issue Oct 13, 2018
- merged with the latest wsrep_api.h
- removed even more outdated code.
janlindstrom pushed a commit to MariaDB/galera that referenced this issue Oct 13, 2018
janlindstrom pushed a commit to MariaDB/galera that referenced this issue Oct 13, 2018
…tion from originator node in pa_range field of the writeset. This allows us to limit pa_range prior to guessing it in certification. This should prevent streaming replication fragments applying in parallel.
janlindstrom pushed a commit to MariaDB/galera that referenced this issue Oct 13, 2018
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

1 participant