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

Ensure that the concurrency suite actually awaits replication between workloads

    XMLWordPrintable

Details

    • Task
    • Status: Closed
    • Major - P3
    • Resolution: Fixed
    • 3.1.8
    • 3.2.0-rc0
    • Testing Infrastructure
    • None
    • Fully Compatible
    • TIG A (10/09/15)

    Description

      As milkie pointed out, it's possible for the writeConcern write in jstests/concurrency/fsm_libs/cluster.js to fail to run if a failover is occurring and there's no primary:

      this.executeOnMongodNodes(function (db) {
          // Execute on all primary nodes
          if (db.isMaster().ismaster) {
              // Insert a document with a writeConcern for all nodes in the replica set to
              // ensure that all previous workload operations have completed on secondaries
              var result = db.getSiblingDB('test').fsm_teardown.insert({ a: 1 }, wc);
              assert.writeOK(result, 'teardown insert failed: ' + tojson(result));
              assert(db.getSiblingDB('test').fsm_teardown.drop(), 'teardown drop failed');
          }
      });
      

      We should fail with a clear error message if the branch is not executed at all (because of a transient lack of a primary).

      Attachments

        Activity

          People

            jonathan.abrahams Jonathan Abrahams
            kamran.khan Kamran K.
            Votes:
            0 Vote for this issue
            Watchers:
            4 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: