[SERVER-5128] First query via mongos fails with slaveOk if replica set doesn't have a master Created: 28/Feb/12  Updated: 11/Oct/17  Resolved: 11/Oct/17

Status: Closed
Project: Core Server
Component/s: Sharding
Affects Version/s: 3.0.15
Fix Version/s: 3.4.0

Type: Bug Priority: Major - P3
Reporter: Greg Studer Assignee: Kaloian Manassiev
Resolution: Done Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Related
is related to SERVER-4921 replica_set_shard_version.js failing ... Closed
Backwards Compatibility: Fully Compatible
Operating System: ALL
Participants:

 Description   

... see title. Not sure if subsequent queries can fail as well. Issue is the creation of the replica set monitor seems to require a master.



 Comments   
Comment by Githook User [ 11/Oct/17 ]

Author:

{'email': 'kaloian.manassiev@mongodb.com', 'name': 'Kaloian Manassiev', 'username': 'kaloianm'}

Message: SERVER-5128/SERVER-5130 Modify js test to validate both tickets are fixed

Also gets rid of one unnecessary noPassthroughWithMongod test.
Branch: master
https://github.com/mongodb/mongo/commit/d40e4b4104060ae92d618e32d49eccf30f4be73c

Comment by Mathias Stearn [ 06/Mar/14 ]

I think it should be fixed, but worth testing the full stack to ensure that something above the ReplicaSetMonitor isn't broken.

Comment by Greg Studer [ 06/Mar/14 ]

redbeard0531 - is this still an issue given the ReplicaSetMonitor refactor?

Comment by Emanuele Bragagnolo [ 29/Feb/12 ]

I notice a similar issue with java driver

I hope this thread could help.

http://groups.google.com/group/mongodb-user/browse_thread/thread/aae21794982aace9/3b6411bc35b7c311?lnk=gst&q=emanuele.bragagnolo#3b6411bc35b7c311

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