[SERVER-1543] slave can't be queried during failover Created: 02/Aug/10  Updated: 12/Jul/16  Resolved: 25/Aug/10

Status: Closed
Project: Core Server
Component/s: Replication
Affects Version/s: None
Fix Version/s: 1.6.2, 1.7.0

Type: Bug Priority: Minor - P4
Reporter: Kristina Chodorow (Inactive) Assignee: Kristina Chodorow (Inactive)
Resolution: Done Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Operating System: ALL
Participants:

 Description   

If you start 3 servers and then set slaveOk on one of the slaves, then kill the primary, there are a couple seconds where querying the slave doesn't work:

> b1.getMongo().setSlaveOk()
> b1.bar.find() // querying the slave works
> b1.bar.find()
> b1.bar.find()
> b1.bar.find() // kill the master
error:

{ "$err" : "not master", "code" : 10107 }

> b1.bar.find()
error:

{ "$err" : "not master", "code" : 10107 }

> b1.bar.find()
error:

{ "$err" : "not master", "code" : 10107 }

> b1.bar.find()
error:

{ "$err" : "not master", "code" : 10107 }

> b1.bar.find()
error:

{ "$err" : "not master", "code" : 10107 }

> b1.bar.find()
error:

{ "$err" : "not master", "code" : 10107 }

> b1.bar.find()
error:

{ "$err" : "not master", "code" : 10107 }

> b1.bar.find()
error:

{ "$err" : "not master", "code" : 10107 }

> b1.bar.find()
error:

{ "$err" : "not master", "code" : 10107 }

> b1.bar.find()
error:

{ "$err" : "not master", "code" : 10107 }

> b1.bar.find() // querying the slave works again
> b1.bar.find()
> b1.bar.find()
> b1.bar.find()

I'm having a hard time writing an automatic test that reproduces this, but I'll commit it when I get it working.



 Comments   
Comment by Kristina Chodorow (Inactive) [ 25/Aug/10 ]

Seems to work now!

Comment by Dwight Merriman [ 12/Aug/10 ]

please try now - or ideally make a test. assigning to you to make a test, if it is broken, please assign back to me thanks.

Comment by Dwight Merriman [ 02/Aug/10 ]

this is definitely happening

it's a bit intentional, although suboptimal and should be fixed at least for some scenarios.,

Generated at Thu Feb 08 02:57:19 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.