[SERVER-35997] Await replication on config server after shardCollection in safe secondary reads tests - MongoDB Jira

XML

Word

Printable

JSON

Details

Type: Bug
Status: Closed
Priority: Major - P3
Resolution: Fixed
Affects Version/s: None
Fix Version/s: 3.6.6, 4.0.1, 4.1.1
Component/s: Sharding
Labels:
None

Backwards Compatibility:
Fully Compatible
Operating System:
ALL
Backport Requested:

v4.0, v3.6
Sprint:
Sharding 2018-07-16
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.

Attachments

Activity

People

Assignee:: Matthew Saltz (Inactive)

Reporter:: Janna Golden

Participants:: Githook User, Janna Golden, Matthew Saltz

Votes:: 0 Vote for this issue

Watchers:: 3 Start watching this issue

Dates

Created:: Jul 06 2018 06:00:47 PM UTC

Updated:: Jul 20 2018 10:20:09 PM UTC

Resolved:: Jul 06 2018 06:25:35 PM UTC