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

"Fatal Assertion 16360" triggered by temporary collections dropped when restarted in standalone mode

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Major - P3
    • Resolution: Fixed
    • Affects Version/s: 3.2.7
    • Fix Version/s: 3.2.13, 3.4.5, 3.5.3
    • Component/s: Replication
    • Labels:
    • Backwards Compatibility:
      Fully Compatible
    • Operating System:
      ALL
    • Backport Requested:
      v3.4, v3.2
    • Sprint:
      TIG 2017-02-13
    • Case:

      Description

      Scenario:

      During the process of Changing the Size of the Oplog, one step is to Restart a Secondary in Standalone Mode on a Different Port.

      After the change, when the node is Restarted again as a part of the replica set, the fatal assertion may be triggered. The fatal assertion itself is covered under SERVER-23390.

      However, the issue in this case is caused by the behavior of tmp.agg_out temporary collections which are cleaned after the restart of the mongod server.

      [repl writer worker 14] writer worker caught exception:  :: caused by :: 26 Failed to apply insert due to missing collection: { ts: Timestamp 1476945662000|9194, t: 112, h: 3665423956733067926, v: 2, op: "i", ns: "db1.tmp.agg_out.81", o: ...
       
      [repl writer worker 14] Fatal Assertion 16360
      

        Attachments

          Issue Links

            Activity

              People

              • Votes:
                0 Vote for this issue
                Watchers:
                10 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: