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

stale_mongos_updates_and_removes.js can fail because data isn't replicated fast enough

    • Type: Icon: Bug Bug
    • Resolution: Done
    • Priority: Icon: Major - P3 Major - P3
    • 3.3.5
    • Affects Version/s: None
    • Component/s: Sharding
    • None
    • Fully Compatible
    • ALL
    • Sharding 13 (04/22/16)
    • 0

      stale_mongos_updates_and_removes.js uses two mongos, setting one up as stale before testing operation correctness. During setup, however, the moveChunk call on the second mongos to make the first stale fails because shardCollection was executed on the first and the second runs into a collection not sharded error. So need to add an awaitReplication on the config replset before making the first mongos stale.

            Assignee:
            dianna.hohensee@mongodb.com Dianna Hohensee (Inactive)
            Reporter:
            dianna.hohensee@mongodb.com Dianna Hohensee (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated:
              Resolved: