Uploaded image for project: 'Core Server'
  1. Core Server
  2. SERVER-44679

Rollback fuzzer must account for transactions that may not have been rolled back.

XMLWordPrintableJSON

    • Type: Icon: Bug Bug
    • Resolution: Duplicate
    • Priority: Icon: Major - P3 Major - P3
    • None
    • Affects Version/s: None
    • Component/s: None
    • Labels:
      None
    • ALL
    • Repl 2019-12-16, Repl 2019-12-30, Repl 2020-01-13
    • 6

      We already take into account that some rollbacks may not occur during rollback shutdown tests

      https://github.com/mongodb/mongo/blob/103318868c860e441050652b6dae137d0d21d593/jstests/replsets/libs/rollback_test.js#L215

      However, we don't take into account that these rollbacks that don't happen may include prepared transactions, which prevent us from doing data consistency checks. In rollback tests with shutdowns we must account for rolled-back prepared transactions possibly still being around, and abort them explicitly or skip consistency checks.

            Assignee:
            pavithra.vetriselvan@mongodb.com Pavithra Vetriselvan
            Reporter:
            matthew.russotto@mongodb.com Matthew Russotto
            Votes:
            0 Vote for this issue
            Watchers:
            9 Start watching this issue

              Created:
              Updated:
              Resolved: