[SERVER-2439] Queries still being routed to slave even though down Created: 30/Jan/11 Updated: 12/Jul/16 Resolved: 31/Jan/11 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Replication |
| Affects Version/s: | 1.7.5 |
| Fix Version/s: | 1.7.6 |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | David Mytton | Assignee: | Kristina Chodorow (Inactive) |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Attachments: |
|
| Operating System: | Linux |
| Participants: |
| Description |
|
For some queries we use slaveOkay in the PHP driver. However, on shutting down the secondary, queries were still being routed to it even after the 5 second timeout (as per http://www.php.net/manual/en/mongo.queries.php). During this time rs3b was down and rs3a was up as the primary. rs3c and rs3d are also up but are hidden so are not used for slave queries. Since reads are randomly distributed some queries were returning whilst others were erroring. set3:PRIMARY> rs.status() , , , , , |
| Comments |
| Comment by auto [ 31/Jan/11 ] |
|
Author: {u'login': u'kchodorow', u'name': u'Kristina', u'email': u'kristina@10gen.com'}Message: more aggressive about checking for slave errors |