[SERVER-16598] Add general mechanism for invalidating ongoing ops after a drop Created: 18/Dec/14  Updated: 23/Sep/19  Resolved: 07/May/18

Status: Closed
Project: Core Server
Component/s: Internal Code
Affects Version/s: 2.8.0-rc3
Fix Version/s: None

Type: Improvement Priority: Major - P3
Reporter: Randolph Tan Assignee: Randolph Tan
Resolution: Incomplete Votes: 0
Labels: todo_in_code
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Related
related to SERVER-43436 Remove outdated todo comment Closed
Participants:

 Description   

Currently, anything using the creates a cursor can check if the cursor gets invalidated to determine if a drop occurred. We should also have something similar for other ops that doesn't need a cursor (for example, the Cloner).



 Comments   
Comment by Andy Schwerin [ 08/Oct/15 ]

renctan, can you explain this in more detail? Do you still see a need for something, here?

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