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.
stale_mongos_updates_and_removes.js can fail because data isn't replicated fast enough
- Assignee:
-
Dianna Hohensee (Inactive)
- Reporter:
-
Dianna Hohensee (Inactive)
- Votes:
-
0 Vote for this issue
- Watchers:
-
3 Start watching this issue
- Created:
- Updated:
- Resolved: