[SERVER-61912] Investigate rescanning an index vs processing concurrent writes after interrupt during unique index conversion Created: 03/Dec/21  Updated: 27/Oct/23  Resolved: 27/Feb/23

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

Type: Task Priority: Major - P3
Reporter: Pavithra Vetriselvan Assignee: Backlog - Storage Execution Team
Resolution: Gone away Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Related
is related to SERVER-61486 Investigate work needed to track dupl... Closed
Assigned Teams:
Storage Execution
Participants:

 Description   

In the implementation for SERVER-61486, interrupting the unique index collMod request will stop tracking concurrent writes. It's possible that it would be more work to process all the concurrent writes than the rescan the index based on how much concurrent activity there is.



 Comments   
Comment by Connie Chen [ 27/Feb/23 ]

The tracker that this ticket was meant to optimize is no longer around, so closing this as "gone away"

Comment by Pavithra Vetriselvan [ 04/Feb/22 ]

Tracking concurrent writes is not useful to the migration case or DR case, so I'm taking this ticket out of the project. We can re-evaluate whether this is useful in the general case later and schedule accordingly.

Generated at Thu Feb 08 05:53:39 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.