Handle CappedPositionLost during tenant migrations

XMLWordPrintableJSON

    • Type: Task
    • Resolution: Won't Fix
    • Priority: Major - P3
    • None
    • Affects Version/s: None
    • Component/s: None
    • None
    • Serverless
    • None
    • 3
    • None
    • None
    • None
    • None
    • None
    • None

      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.

            Assignee:
            [DO NOT USE] Backlog - Server Serverless (Inactive)
            Reporter:
            A. Jesse Jiryu Davis
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated:
              Resolved: