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

ReplSetTest.checkReplicaSet fails when run against a config server replica set.

    XMLWordPrintable

Details

    • Bug
    • Status: Closed
    • Minor - P4
    • Resolution: Duplicate
    • 3.4.11
    • None
    • JavaScript, Replication, Sharding
    • None
    • ALL
    • 0

    Description

      checkReplicaSet fails with the following message:

      w:'majority' is the only valid write concern when writing to config servers

      This is failing as part of the validation checking at the end of the 3.4 testsuite.

      Attachments

        Issue Links

          duplicates

          Bug - A problem which impairs or prevents the functions of the product. SERVER-33068 run_check_repl_dbhash.js hook exits without actually running dbhash on a replica set

          • Critical - P2 - Crashes, loss of data, severe memory leak.
          • Closed

          Bug - A problem which impairs or prevents the functions of the product. SERVER-30900 remove collMod writeConcern argument from ReplSetTest.checkReplicaSet()

          • Major - P3 - Major loss of function.
          • Closed

          Task - A task that needs to be done. SERVER-21630 Expand resmoke's CheckReplDBHash support to config servers and sharded replica sets

          • Major - P3 - Major loss of function.
          • Closed

          Task - A task that needs to be done. SERVER-31441 Make run_validate_collections.js validate all nodes in replica set in parallel

          • Major - P3 - Major loss of function.
          • Closed

          Improvement - An improvement or enhancement to an existing feature or task. SERVER-24759 Run resmoke.py collection validation on the config servers

          • Major - P3 - Major loss of function.
          • Closed

          Improvement - An improvement or enhancement to an existing feature or task. SERVER-28989 Avoid dropping dummy database in ReplSetTest.prototype.checkReplicaSet()

          • Major - P3 - Major loss of function.
          • Closed

          Activity

            People

              max.hirschhorn@mongodb.com Max Hirschhorn
              jim.oleary@mongodb.com James O'Leary
              Votes:
              0 Vote for this issue
              Watchers:
              5 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: