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

Temporary Collections created through oplog application, but not through client commands

    • Type: Icon: Bug Bug
    • Resolution: Unresolved
    • Priority: Icon: Minor - P4 Minor - P4
    • None
    • Affects Version/s: 3.5.12
    • Component/s: Replication
    • Replication
    • ALL
    • 0

      The rollback fuzzer caught an issue when doing data validation cross a replica set that rolls back (an instance of RollbackTest) some operations and a "control group" replica set that does not roll back, there seemed to have been an issue where a temporary collection only exists on the replica set that did a rollback.

      The "control group" replica set has 2 nodes to avoid differing behavior wrt. temporary collections one a standalone or single node replicates.

      This suggests there's behavioral difference between oplog application vs commands performed directly by a client.

      The failure is reproducible by downloading the js file attached to this ticket and running ./mongo --nodb rollback_test-convertToCapped.js

      After chatting with judah.schvimer, I'm filing this ticket for future reference, but it may not be something that needs to be looked into in the immediate future.

            Assignee:
            backlog-server-repl [DO NOT USE] Backlog - Replication Team
            Reporter:
            robert.guo@mongodb.com Robert Guo (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            6 Start watching this issue

              Created:
              Updated: