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

Potential data consistency issue with implicitly replicated collections

    • Type: Icon: Bug Bug
    • Resolution: Gone away
    • Priority: Icon: Major - P3 Major - P3
    • None
    • Affects Version/s: None
    • Component/s: None
    • Replication
    • ALL
    • Execution Team 2023-12-11, Execution Team 2023-12-25, Execution Team 2024-01-08, Execution Team 2024-01-22
    • 5

      Implicitly replicated collections are a set of internal collections that participate in oplog replication partially by only replicating deletes. Inserts to these collections are implicit by other writes to potentially different collections.

      This behaviour however, can result in inconsistency during secondary oplog application. Suppose the following scenario:

      • T1 writes to collA, which implicitly inserts to impA (implicitly replicated)
      • T2 deletes the insert performed to impA

      In this case both T2 and T1 will be executed in parallel during oplog replication on the secondary if they are part of the same batch. This might lead to the delete operation being performed before the insert. As a result, the document will not exist on the primary but survive on the secondary.

            Assignee:
            wei.hu@mongodb.com Wei Hu
            Reporter:
            jordi.olivares-provencio@mongodb.com Jordi Olivares Provencio
            Votes:
            0 Vote for this issue
            Watchers:
            16 Start watching this issue

              Created:
              Updated:
              Resolved: