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

recover_prepared_txn_with_multikey_write.js should make sure no prepare conflicts are generated on catalog object after restarting node

    XMLWordPrintable

    Details

    • Type: Improvement
    • Status: Closed
    • Priority: Major - P3
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: 4.2.1, 4.3.1
    • Component/s: Replication
    • Labels:
      None
    • Backwards Compatibility:
      Fully Compatible
    • Backport Requested:
      v4.2
    • Linked BF Score:
      43

      Description

      The recover_prepared_txn_with_multikey_write.js test reconstructs a prepared transaction that did a multikey write. After reconstructing this transaction, we should assert that no prepare conflicts are generated on the catalog, to make sure that the transaction was reconstructed correctly and the multikey write was done in a side transaction. This may have helped catch the issue referenced in SERVER-42750. We should also make sure it waits for the restarted node to become primary again, so that data consistency checks are not skipped inside stopSet. Furthermore, it should abort the prepared transaction before shutting down the set.

        Attachments

          Issue Links

            Activity

              People

              Assignee:
              william.schultz William Schultz (Inactive)
              Reporter:
              william.schultz William Schultz (Inactive)
              Participants:
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

                Dates

                Created:
                Updated:
                Resolved: