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

Reevaluate not_allowed_on_sharded_collection_cmd.js testing

    XMLWordPrintable

Details

    • Fully Compatible
    • ALL
    • v4.0, v3.6
    • Sharding 2018-09-24
    • 34

    Description

      to whether include testing with "stale mongos". movePrimary can currently cause multiple mongos to be out of sync until they refresh their ShardRegistry. So the test could be trying to test a behavior that is known to be undefined.

      Our docs already has the proper warning:

      If you use the movePrimary command to move un-sharded collections, you must either restart all mongos instances, or use the flushRouterConfig command on all mongos instances before reading or writing any data to any unsharded collections that were moved. This action ensures that the mongos is aware of the new shard for these collections.

      Attachments

        Issue Links

          Activity

            People

              randolph@mongodb.com Randolph Tan
              randolph@mongodb.com Randolph Tan
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: