[SERVER-1710] cursor tracking is not database aware Created: 31/Aug/10  Updated: 12/Jul/16  Resolved: 31/Aug/10

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

Type: Bug Priority: Blocker - P1
Reporter: Eliot Horowitz (Inactive) Assignee: Eliot Horowitz (Inactive)
Resolution: Done Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
Operating System: ALL
Participants:

 Description   

We track cursors by object location so if an object is deleted we can advance.
We weren't keep these isolated by db, so if a cursor is open at position X on db A, and a delete on db B removes an object at position X, a segfault can happen because a cursor will be advanced to an illegal position.

This is exacerbated by replication because once an oplog rolls over, every time we add an op, we delete one, so it makes the odds of this higher.



 Comments   
Comment by Eliot Horowitz (Inactive) [ 31/Aug/10 ]

commit e070747d94e0dccfcab5ba2e385eb699c6993796

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