[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: |
|
||||||||
| 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: Also gets rid of one unnecessary noPassthroughWithMongod test. |
| 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. |