[SERVER-2481] SlaveOK queries shouldn't go to slaves in RECOVERING state Created: 04/Feb/11 Updated: 12/Jul/16 Resolved: 16/Jun/11 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Sharding |
| Affects Version/s: | None |
| Fix Version/s: | 1.8.3, 1.9.1 |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Mathias Stearn | Assignee: | Greg Studer |
| Resolution: | Done | Votes: | 2 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||
| Operating System: | ALL | ||||
| Participants: | |||||
| Description |
|
mongo shell connected to mongos with single replica set shard > db.foo.find().itcount() > db.getMongo().slaveOk = false connecting directly to replSet: rs.status() , , , , , , , |
| Comments |
| Comment by auto [ 11/Jul/11 ] |
|
Author: {u'login': u'gregstuder', u'name': u'gregs', u'email': u'greg@10gen.com'}Message: backport of fix for |
| Comment by auto [ 16/Jun/11 ] |
|
Author: {u'login': u'gregstuder', u'name': u'gregs', u'email': u'greg@10gen.com'}Message: better logic for no-result in rs for parallel ops |
| Comment by auto [ 16/Jun/11 ] |
|
Author: {u'login': u'gregstuder', u'name': u'gregs', u'email': u'greg@10gen.com'}Message: tests for parallel cursor and failover |
| Comment by auto [ 16/Jun/11 ] |
|
Author: {u'login': u'gregstuder', u'name': u'gregs', u'email': u'greg@10gen.com'}Message: parallel cursor recover gracefully from replica set and other errors |
| Comment by Greg Studer [ 06/Jun/11 ] |
|
New parallel cursor has this behavior as well. |
| Comment by Greg Studer [ 01/Jun/11 ] |
|
Wrong ticket for commit, but this addresses the problem (had two jira cases open) Author: {u'login': u'gregstuder', u'name': u'gregs', u'email': u'greg@10gen.com'}Message: check for not master or secondary error on slave queries, re-route |
| Comment by Y. Wayne Huang [ 23/May/11 ] |
|
any updates on this? it makes slaveOk unusable. |