Workaround for SERVER-78311 - Add a read concern majority check after MongoRestore.CreateCollection

XMLWordPrintableJSON

    • Type: Task
    • Resolution: Unresolved
    • Priority: Major - P3
    • None
    • Affects Version/s: None
    • Component/s: mongorestore
    • 2
    • Tools and Replicator
    • 6

      Due to SERVER-78311, the server can return OK for a create collection command even though the create failed majority write concern. When mongorestore creates the collection, and the collection is only created on the primary and the primary is rolled back, the collection will be missing but mongo restore will not receive any error from the server, so any documents removed by the rollback cannot be recovered. This would be a silent failure and users would not know that some documents are missing.

      We need to work around this by doing a majority read right after the CreateCollection command in order to make sure the collection has been committed to a majority of nodes.

      More context in additional assessment - https://docs.google.com/document/d/1ZnxDWsPU-aaAp3Tsc8f7auFaOpuc_VzaHnemBKq52l8/edit?tab=t.0#heading=h.4s5m7uvq8w0w

            Assignee:
            Unassigned
            Reporter:
            Shyam Subramaniyam
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated: