[SERVER-2479] KillCursor always sent to master and never the slave Created: 04/Feb/11 Updated: 12/Jul/16 Resolved: 05/Feb/11 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Internal Client |
| Affects Version/s: | None |
| Fix Version/s: | 1.7.6 |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Mathias Stearn | Assignee: | Eliot Horowitz (Inactive) |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Operating System: | ALL |
| Participants: |
| Description |
|
client/dbclient_rs.cpp if any cursored query has been send to a slave we should probably send the killCursor message to the slave as well. One issue could be the possibility of master and slave using the same cursorID for different queries, but that would negatively effect the current implementation as well. |
| Comments |
| Comment by auto [ 05/Feb/11 ] |
|
Author: {u'login': u'erh', u'name': u'Eliot Horowitz', u'email': u'eliot@10gen.com'}Message: DBClientReplicaSet::killCursor should never be called |