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

Make multi_mongos2.js awaitReplication after sharding a collection

    • Fully Compatible
    • v4.2
    • 11

      In this test we shard a collection through one router and expect another router to know that the collection is sharded. However, the second router can refresh its cache from a config server secondary, so if the config server has not replicated that the collection is sharded, the second router may refresh and think that the collection is unsharded. We should fix all instances of this assumption in this test by adding awaitReplication after sharding a collection.

            Assignee:
            blake.oler@mongodb.com Blake Oler
            Reporter:
            matthew.saltz@mongodb.com Matthew Saltz (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: