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

Batched oplog application increases frequency of idempotency violations

    • Fully Compatible
    • ALL

      In 2.0.x, oplog entries are applied one at a time on each secondary. Thus, on a restart after a shutdown, only a single op can be applied twice. In 2.2.0, ops are applied in batches, so on a restart, potentially all the ops in the last batch can be reapplied. There are certain sequences of ops that violate idempotency guarantees needed to insure proper replication. In 2.2.0, if we detect such a sequence, the secondary halts replication and shuts down, unable to come back online.

        1. mongod.log
          6 kB
          Rotem Hermon

            Assignee:
            alerner Alberto Lerner
            Reporter:
            ian@mongodb.com Ian Whalen (Inactive)
            Votes:
            9 Vote for this issue
            Watchers:
            19 Start watching this issue

              Created:
              Updated:
              Resolved: