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

Test cases in txn_commit_optimizations_for_read_only_shards.js are not isolated from each other

    • Cluster Scalability
    • 5
    • 4

      Each of the test case touches different documents which in theory should not conflict with each other. However, due to SERVER-40176, it can cause new test cases to hit prepare conflict if transactions from older test cases are still alive. This jstest also sets the coordinateCommitReturnImmediatelyAfterPersistingDecision to true, which allows returning early and if combined with stop replication for certain test cases, can cause the older transaction to stay alive longer than expected. The combination SERVER-40176 and prepare transactions living longer than expected can cause spurious failures in the test.

            backlog-server-cluster-scalability Backlog - Cluster Scalability
            randolph@mongodb.com Randolph Tan
            0 Vote for this issue
            0 Start watching this issue