[SERVER-41777] Make multi_mongos2.js awaitReplication after sharding a collection Created: 14/Jun/19 Updated: 29/Oct/23 Resolved: 16/Jul/19 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Sharding |
| Affects Version/s: | None |
| Fix Version/s: | 4.3.1, 4.2.6 |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Matthew Saltz (Inactive) | Assignee: | Blake Oler |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | neweng, sharding-wfbf-day | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Backwards Compatibility: | Fully Compatible | ||||||||
| Backport Requested: |
v4.2
|
||||||||
| Participants: | |||||||||
| Linked BF Score: | 11 | ||||||||
| Description |
|
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. |
| Comments |
| Comment by Githook User [ 13/Apr/20 ] |
|
Author: {'name': 'Blake Oler', 'email': 'blake.oler@mongodb.com', 'username': 'BlakeIsBlake'}Message: (cherry picked from commit bfe2e00fabc343c527f4eb3ab62be844ac4c02d3) |
| Comment by Githook User [ 16/Jul/19 ] |
|
Author: {'name': 'Blake Oler', 'username': 'BlakeIsBlake', 'email': 'blake.oler@mongodb.com'}Message: |