[JAVA-219] return no data when slaves are down Created: 20/Nov/10  Updated: 04/Dec/13  Resolved: 16/May/11

Status: Closed
Project: Java Driver
Component/s: Cluster Management
Affects Version/s: 2.3
Fix Version/s: None

Type: Bug Priority: Major - P3
Reporter: Joseph Wang Assignee: Scott Hernandez (Inactive)
Resolution: Done Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

linux



 Description   

Two of secondary nodes are out of sync. However, the primary has the latest data.

> rs.status()
{
"set" : "lp",
"date" : "Fri Nov 19 2010 15:54:38 GMT-0800 (PST)",
"myState" : 1,
"members" : [

{ "_id" : 0, "name" : "stage1.vpc3.estalea.net:4101", "health" : 1, "state" : 1, "self" : true }

,

{ "_id" : 1, "name" : "stage1.vpc3.estalea.net:4102", "health" : 1, "state" : 2, "uptime" : 3653, "lastHeartbeat" : "Fri Nov 19 2010 15:54:37 GMT-0800 (PST)", "errmsg" : "error RS102 too stale to catch up" }

,

{ "_id" : 2, "name" : "stage1.vpc3.estalea.net:4103", "health" : 1, "state" : 2, "uptime" : 3651, "lastHeartbeat" : "Fri Nov 19 2010 15:54:37 GMT-0800 (PST)", "errmsg" : "error RS102 too stale to catch up" }

cur = coll.find(dbQuery).addOption(
Bytes.QUERYOPTION_SLAVEOK);

return no result.



 Comments   
Comment by Scott Hernandez (Inactive) [ 16/May/11 ]

Please reopen if this is still an issue.

Comment by Scott Hernandez (Inactive) [ 05/Apr/11 ]

We have made some significant changes since 2.3. Can you tests again with 2.5.3 when it comes out today?

Generated at Thu Feb 08 08:51:46 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.