[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:
Related
related to PYTHON-454 MongoReplicaSetClient should refresh ... Closed
related to PYTHON-455 Replica set members not in primary/se... Closed
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 PYTHON-454 to track a fix for this problem. I'm going to close this server ticket since the problem is in PyMongo.

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.

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