Uploaded image for project: 'Percona Server'
  1. Percona Server
  2. PS-4129

START TRANSACTION WITH CONSISTENT SNAPSHOT behaves different

    Details

      Description

      START TRANSACTION WITH CONSISTENT SNAPSHOT behaves different in Percona MyRocks than Facebook MyRocks.

      Consider the following sequence where tx_isolation is either 'repeatable-read' or 'read-committed':

      > create table r1 (id int primary key, value int, value2 int) engine=rocksdb;
      > set session tx_isolation='<level>';
      > start transaction with consistent snapshot;
      > insert into r1 values(11,11,11);
      

      InnoDB succeeds for both modes.
      Upstream Facebook MyRocks succeeds for 'read-committed' and fails with a read-only violation for 'repeatable-read'.
      Percona MyRocks fails with a read-only violation for both.

      Why the difference? Is this acceptable? Doc?

      This comes from the tests:
      rocksdb.cons_snapshot_repeatable_read
      rocksdb.cons_snapshot_read_committed
      and is implemented in ./mysql-test/suite/rocksdb/include/consistent_snapshot.inc

        Smart Checklist

          Attachments

            Activity

              People

              • Assignee:
                george.lorch George Lorch
                Reporter:
                george.lorch George Lorch
              • Votes:
                0 Vote for this issue
                Watchers:
                1 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: