Commit timestamp can be less than stable timestamp for running transactions, in specific scenario

XMLWordPrintableJSON

    • Type: Bug
    • Resolution: Won't Fix
    • Priority: Minor - P4
    • None
    • Affects Version/s: None
    • Component/s: None
    • None
    • Storage Engines 2019-03-25, Storage Engines 2019-05-06
    • 8

      Currently the following scenario is possible within wired tiger

      self.conn.set_timestamp('stable_timestamp=6');
      session1.begin_transaction()

      session1.timestamp_transaction('commit_timestamp=7')

      self.conn.set_timestamp('stable_timestamp=8')

      cur1[1] = 4

      session1.commit_transaction()

       

      This presents an issue as if we check pointed at stable timestamp 8 we couldn't guarantee what would be part of the checkpoint.

              Assignee:
              Luke Pearson
              Reporter:
              Luke Pearson
              Votes:
              0 Vote for this issue
              Watchers:
              5 Start watching this issue

                Created:
                Updated:
                Resolved: