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

Run causally consistent resmoke suites with non-voting secondaries

    XMLWordPrintableJSON

Details

    • Sharding 2020-04-20
    • 0

    Description

      In testing changes for SERVER-31670, setting secondaries to have zero votes causes some tests in the causally consistent passthrough suites to fail complaining that the afterClusterTime sent to a secondary is after the clusterTime on the secondary.

      As a temporary fix, we are not giving secondaries zero votes in those suites. These failures should be investigated, and the voting_secondaries: true options should be removed from the causally_consistent*.yml configs.

      Attachments

        Issue Links

          depends on

          Bug - A problem which impairs or prevents the functions of the product. SERVER-34597 shardedcluster.py does not wait correctly on shards initialization

          • Major - P3 - Major loss of function.
          • Closed
          is related to

          Bug - A problem which impairs or prevents the functions of the product. SERVER-31670 Change replica set fixture used by replica_sets_jscore_passthrough to make its secondary have zero votes

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

          Task - A task that needs to be done. SERVER-32775 Investigate afterClusterTime error in causally consistent suite with 0 vote secondaries

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

          Activity

            People

              max.hirschhorn@mongodb.com Max Hirschhorn
              kevin.albertson@mongodb.com Kevin Albertson
              Votes:
              0 Vote for this issue
              Watchers:
              6 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: