[SERVER-61345] Handle CappedPositionLost during tenant migrations Created: 09/Nov/21  Updated: 06/Dec/22  Resolved: 15/Nov/21

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

Type: Task Priority: Major - P3
Reporter: A. Jesse Jiryu Davis Assignee: [DO NOT USE] Backlog - Server Serverless (Inactive)
Resolution: Won't Fix Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Related
is related to SERVER-61308 CappedPositionLost if capped collecti... Closed
Assigned Teams:
Serverless
Participants:

 Description   

To fully support capped collections in Serverless phase 1 we must solve the problem described in SERVER-61308. Otherwise, if a donor has a busy capped collection that's constantly truncating its oldest documents, the donor might be impossible to migrate from: every attempt to migrate would die of CappedPositionLost.

If we choose not to fix this we should ban capped collections from Serverless.


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