[SERVER-13673] Localize locking at plan stage boundary Created: 22/Apr/14  Updated: 20/Jan/15  Resolved: 20/Jan/15

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

Type: Task Priority: Major - P3
Reporter: Craig Harris Assignee: Craig Harris
Resolution: Won't Fix Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Tested
Participants:

 Description   

Refactor DeleteExecutor and UpdateExecutor into two stages: one that locates the documents to modify and one that does the modifications; and packaged the stages in a runner.

Move locking above DeleteExecutor into the new modification stages.

Lay the groundwork by repackaging CachedPlanRunner and DeletePlanRunner as stages in their own right.



 Comments   
Comment by Ramon Fernandez Marina [ 20/Jan/15 ]

This work is no longer relevant.

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