[SERVER-20294] Race condition in shard targeting logic results in "Shard not found" error Created: 04/Sep/15  Updated: 25/Jan/17  Resolved: 09/Sep/15

Status: Closed
Project: Core Server
Component/s: Sharding
Affects Version/s: 3.1.7
Fix Version/s: 3.1.8

Type: Bug Priority: Major - P3
Reporter: David Storch Assignee: Spencer Brody (Inactive)
Resolution: Done Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
is depended on by SERVER-20067 Shell should decide whether or not to... Closed
Related
related to SERVER-20270 Race condition around updating config... Closed
Backwards Compatibility: Fully Compatible
Operating System: ALL
Steps To Reproduce:

python buildscripts/resmoke.py --shellReadMode=commands jstests/noPassthroughWithMongod/sharding_rs2.js

Participants:

 Comments   
Comment by Githook User [ 11/Sep/15 ]

Author:

{u'username': u'stbrody', u'name': u'Spencer T Brody', u'email': u'spencer@mongodb.com'}

Message: SERVER-20270 SERVER-20294 Make sure to update ShardRegistry's _configServerCS on CSRS membership changes
Branch: master
https://github.com/mongodb/mongo/commit/093c1c0c988752d76bf919ec8a6e85ae257964c2

Comment by Githook User [ 09/Sep/15 ]

Author:

{u'username': u'stbrody', u'name': u'Spencer T Brody', u'email': u'spencer@mongodb.com'}

Message: SERVER-20294 Update ShardRegistry on-demand on changes to shard replica set membership
Branch: master
https://github.com/mongodb/mongo/commit/5a54d7b9efcd63316c167f4f8c2b68348150b6b6

Comment by Spencer Brody (Inactive) [ 04/Sep/15 ]

This is basically the exact same issue as SERVER-20270, just for shards instead of the config servers

Generated at Thu Feb 08 03:53:46 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.