[SERVER-6052] Investigate killop in ClientCursor::aboutToDelete() Created: 09/Jun/12  Updated: 07/Dec/15  Resolved: 07/Dec/15

Status: Closed
Project: Core Server
Component/s: Concurrency
Affects Version/s: None
Fix Version/s: None

Type: Task Priority: Major - P3
Reporter: Aaron Staple Assignee: Unassigned
Resolution: Done Votes: 0
Labels: ntc
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Related
is related to SERVER-5999 page fault exception in ClientCursor:... Closed
Participants:

 Description   

I think there may be a case similar to SERVER-5999 where a kill op request to a remove operation that has not yet performed a write can trigger an interrupt exception inside a cursor advance() in ClientCursor::aboutToDelete(). This could leave a MultiCursor in an inconsistent state, as in SERVER-5999. Worth investigating and fixing if necessary.



 Comments   
Comment by David Storch [ 07/Dec/15 ]

This ticket refers to implementation details of the query system that were replaced in SERVER-10026. Closing as Gone Away.

Generated at Thu Feb 08 03:10:38 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.