Insertion order of capped collections may not be preserved after initial sync

XMLWordPrintableJSON

    • Type: Bug
    • Resolution: Unresolved
    • Priority: Major - P3
    • None
    • Affects Version/s: None
    • Component/s: None
    • None
    • Replication
    • ALL
    • None
    • 3
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      This is a very corner case. But since we ignore duplicateKey during initial sync and during oplog application, I think the following sequence is possible:

      Sync Source Syncing nodes
      Insert 1, 2:
      [1, 2]      		 Clone 1, 2:
      [1, 2]
      Rollover/delete 1:
      [2]      		  
      Insert 1, 3:
      [2, 1, 3]      		 Clone 1, 3
      [1, 2, 3] because duplicateKey on (1) is ignored
        Start oplog application
        Apply delete(1), insert(1), insert(3):
      [2, 3, 1] because duplicateKey on (3) is ignored

       

              Assignee:
              [DO NOT USE] Backlog - Replication Team
              Reporter:
              Lingzhi Deng
              Votes:
              0 Vote for this issue
              Watchers:
              7 Start watching this issue

                Created:
                Updated: