Uploaded image for project: 'Core Server'
  1. Core Server
  2. SERVER-69050

Tenant oplog buffer collection may not get dropped after the migration is marked garbage collectable.

    • Type: Icon: Bug Bug
    • Resolution: Gone away
    • Priority: Icon: Major - P3 Major - P3
    • None
    • Affects Version/s: None
    • Component/s: None
    • Serverless
    • ALL

      Assume, the recipient state doc is marked garbage collectable and majority replicated. Now a stepdown happens but before dropping the oplog buffer. Then, if a new primary steps up, there are chances, ttl can delete the expired state document before the POS machinery is able to read the state document and start the instance and drop the tenant oplog buffer collection. This can result in orphaned tenant oplog buffer collection which can be cleaned up later only by cloud intervention.

            Assignee:
            backlog-server-serverless [DO NOT USE] Backlog - Server Serverless (Inactive)
            Reporter:
            suganthi.mani@mongodb.com Suganthi Mani
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated:
              Resolved: