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

Figure out mixed version replication for config.transactions

XMLWordPrintableJSON

    • Type: Icon: Task Task
    • Resolution: Gone away
    • Priority: Icon: Major - P3 Major - P3
    • None
    • Affects Version/s: None
    • Component/s: None
    • None
    • Sharding

      In v4.0 secondary replication updates for config.transactions are expressed as replacement updates. This can be an issue for v4.0 secondaries when trying to replicate an oplog history that contains writes for newer versions since the replacement updates can accidentally remove fields that was not included in the replacement update request.

            Assignee:
            backlog-server-sharding [DO NOT USE] Backlog - Sharding Team
            Reporter:
            randolph@mongodb.com Randolph Tan
            Votes:
            0 Vote for this issue
            Watchers:
            4 Start watching this issue

              Created:
              Updated:
              Resolved: