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

Concurrency stepdown suites should wait for replication of workload setups before starting stepdown thread

    XMLWordPrintable

Details

    • Bug
    • Status: Closed
    • Major - P3
    • Resolution: Fixed
    • None
    • 4.0.2, 4.1.2
    • Testing Infrastructure
    • None
    • Fully Compatible
    • ALL
    • v4.0
    • TIG 2018-08-27
    • 23
    • 3

    Description

      The concurrency stepdown suites wait until after setup has been called for each workload before starting the stepdown thread because the setup methods don't run with overriden majority read/write concern. The effects of each setup are not guaranteed to be majority committed at this point though, so an immediate stepdown can still roll back some of the setup, like the creation of the TTL index in indexed_insert_ttl.js.

      A fix for this would be waiting for replication on all shards and the config server before starting the stepdown thread.

      Attachments

        Activity

          People

            robert.guo@mongodb.com Robert Guo
            jack.mulrow@mongodb.com Jack Mulrow
            Votes:
            0 Vote for this issue
            Watchers:
            4 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: