[SERVER-7977] query being routed to recovering node when read_preference is secondary Created: 18/Dec/12 Updated: 21/Dec/12 Resolved: 21/Dec/12 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Querying |
| Affects Version/s: | 2.2.2 |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Brian Reed | Assignee: | Unassigned |
| Resolution: | Won't Fix | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Environment: |
pymongo 2.4.1, ubuntu 12.0.4.1 - installation from mongodb-10gen repository |
||
| Issue Links: |
|
||||||||||||
| Operating System: | ALL | ||||||||||||
| Participants: | |||||||||||||
| Description |
|
I don't know whether this is because of pymongo. A replicaset, one member primary, one secondary and one recovering. A pymongo query to the primary with read_preference secondary will throw an error OperationFailure: command SON([('count', u'data.RAW.i612411'), ('fields', None), ('query', {})]) failed: node is recovering. It is trying to query the recovering node. |
| Comments |
| Comment by Bernie Hackett [ 21/Dec/12 ] |
|
This is a PyMongo bug, not a core server issue. |
| Comment by Bernie Hackett [ 21/Dec/12 ] |
|
Hi, I opened |
| Comment by Brian Reed [ 18/Dec/12 ] |
|
I'm sorry, the version of mongo should be 2.2.2 |
| Comment by Brian Reed [ 18/Dec/12 ] |
|
This does not happen if read_preference is not secondary. |