[SERVER-23809] stale_mongos_updates_and_removes.js can fail because data isn't replicated fast enough Created: 19/Apr/16 Updated: 26/Apr/16 Resolved: 20/Apr/16 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Sharding |
| Affects Version/s: | None |
| Fix Version/s: | 3.3.5 |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Dianna Hohensee (Inactive) | Assignee: | Dianna Hohensee (Inactive) |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||
| Backwards Compatibility: | Fully Compatible | ||||
| Operating System: | ALL | ||||
| Sprint: | Sharding 13 (04/22/16) | ||||
| Participants: | |||||
| Linked BF Score: | 0 | ||||
| Description |
|
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. |
| Comments |
| Comment by Githook User [ 20/Apr/16 ] |
|
Author: {u'username': u'DiannaHohensee', u'name': u'Dianna Hohensee', u'email': u'dianna.hohensee@10gen.com'}Message: |