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.

Sign up for GitHub

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

Jump to bottom

SR transaction crashes with innodb_snapshot_isolation. #3617

Open
wants to merge 2 commits into
base: 10.6
Choose a base branch
from
Open

SR transaction crashes with innodb_snapshot_isolation. #3617

wants to merge 2 commits into from

Commits on Nov 13, 2024

  1. MDEV-35281 SR transaction crashes with innodb_snapshot_isolation 

    Ignore snapshot isolation conflict during fragment removal, before
streaming transaction commits. This happens when a streaming
transaction creates a read view that precedes the INSERTion of
fragments into the streaming_log table. Fragments are INSERTed
using a different transaction. These fragment are then removed
as part of COMMIT of the streaming transaction. This fragment
removal operation could fail when the fragments were not part
the transaction's read view, thus violating snapshot isolation.
    @sciascid
    sciascid committed Nov 13, 2024
    Configuration menu
    Copy the full SHA
    b890772 View commit details
    Browse the repository at this point in the history

  2. Adapt galera_sr.GCF-572 to make it work with innodb-snapshot-isolation 

    Make galera_sr.GCF-572 behave the same with and without option
innodb-snapshot-isolation. It is sufficient to remove a SELECT
statement from a transaction to delay the creation of the read
view in innodb. Avoiding the detection of a write-write conflict
under innodb-snapshot-isolation.
    @sciascid
    sciascid committed Nov 13, 2024
    Configuration menu
    Copy the full SHA
    ea1ce54 View commit details
    Browse the repository at this point in the history