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

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

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Open
    • Priority: Minor - P4
    • Resolution: Unresolved
    • Affects Version/s: 3.5.12
    • Fix Version/s: Backlog
    • Component/s: Replication
    • Labels:
    • Operating System:
      ALL
    • Linked BF Score:
      0

      Description

      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.

        Attachments

          Activity

            People

            Assignee:
            backlog-server-repl Backlog - Replication Team
            Reporter:
            robert.guo Robert Guo
            Participants:
            Votes:
            0 Vote for this issue
            Watchers:
            6 Start watching this issue

              Dates

              Created:
              Updated: