[SERVER-35997] Await replication on config server after shardCollection in safe secondary reads tests Created: 06/Jul/18 Updated: 29/Oct/23 Resolved: 06/Jul/18 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Sharding |
| Affects Version/s: | None |
| Fix Version/s: | 3.6.6, 4.0.1, 4.1.1 |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Janna Golden | Assignee: | Matthew Saltz (Inactive) |
| Resolution: | Fixed | 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 | ||||||||
| Backport Requested: |
v4.0, v3.6
|
||||||||
| Sprint: | Sharding 2018-07-16 | ||||||||
| Participants: | |||||||||
| Linked BF Score: | 35 | ||||||||
| Description |
|
We should await replication on the config server after shardCollection is called because we read from the nearest config when refreshing, and can potentially read stale metadata. |
| Comments |
| Comment by Githook User [ 20/Jul/18 ] |
|
Author: {'name': 'Matthew Saltz', 'email': 'matthew.saltz@mongodb.com'}Message: (cherry picked from commit d34986b27327810028d15a3a8732211433b32d93) |
| Comment by Githook User [ 06/Jul/18 ] |
|
Author: {'name': 'Matthew Saltz', 'email': 'matthew.saltz@mongodb.com'}Message: (cherry picked from commit d34986b27327810028d15a3a8732211433b32d93) |
| Comment by Githook User [ 06/Jul/18 ] |
|
Author: {'name': 'Matthew Saltz', 'email': 'matthew.saltz@mongodb.com'}Message: |