[SERVER-29337] jstests/sharding/linearizable_read_concern.js should wait for shardIdentity to replicate to all secondaries before issuing secondary reads Created: 23/May/17  Updated: 30/Oct/23  Resolved: 14/Aug/17

Status: Closed
Project: Core Server
Component/s: Replication
Affects Version/s: 3.5.7
Fix Version/s: 3.5.12

Type: Bug Priority: Major - P3
Reporter: Esha Maharishi (Inactive) Assignee: William Schultz (Inactive)
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
Backwards Compatibility: Fully Compatible
Operating System: ALL
Sprint: Repl 2017-08-21
Participants:
Linked BF Score: 0

 Description   

Assigning to the replication backlog and tagging william.schultz, since he authored the test.

This is blocking BF-5461.



 Comments   
Comment by Githook User [ 14/Aug/17 ]

Author:

{'name': 'William Schultz', 'username': 'will62794', 'email': 'william.schultz@mongodb.com'}

Message: SERVER-29337 sharding/linearizable_read_concern.js should wait for shardIdentity to replicate to all
secondaries
Branch: master
https://github.com/mongodb/mongo/commit/895ed7da872f377ac6cfc1933d8d8b93a3df3e7c

Comment by Spencer Brody (Inactive) [ 07/Aug/17 ]

This is causing lots of build failures - william.schultz, can you try to take a look at this in the next day or two?

Generated at Thu Feb 08 04:20:33 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.