[SERVER-26741] "Fatal Assertion 16360" triggered by temporary collections dropped when restarted in standalone mode Created: 24/Oct/16  Updated: 07/Sep/17  Resolved: 27/Jan/17

Status: Closed
Project: Core Server
Component/s: Replication
Affects Version/s: 3.2.7
Fix Version/s: 3.2.13, 3.4.5, 3.5.3

Type: Bug Priority: Major - P3
Reporter: Ankur Raina (Inactive) Assignee: Max Hirschhorn
Resolution: Done Votes: 0
Labels: bkp
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Backports
Gantt Dependency
has to be done before SERVER-27285 Add a jsCore passthrough with a repls... Closed
Related
related to SERVER-23390 Missing collection during replication... Closed
Backwards Compatibility: Fully Compatible
Operating System: ALL
Backport Requested:
v3.4, v3.2
Sprint: TIG 2017-02-13
Participants:
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



 Comments   
Comment by Githook User [ 20/Apr/17 ]

Author:

{u'username': u'visemet', u'name': u'Max Hirschhorn', u'email': u'max.hirschhorn@mongodb.com'}

Message: SERVER-26741 Retain temp collections when node restarted w/o --replSet.

Fixes an issue where temporary collections would be dropped after a
replica set member was restarted as a stand-alone mongod.

(cherry picked from commit 43e9c303c08f73b56490b662b3d11988cafafdf4)
Branch: v3.4
https://github.com/mongodb/mongo/commit/a89d09556e6667bca56d9637cc8cee9fc0bca14b

Comment by Githook User [ 19/Apr/17 ]

Author:

{u'username': u'visemet', u'name': u'Max Hirschhorn', u'email': u'max.hirschhorn@mongodb.com'}

Message: SERVER-26741 Retain temp collections when node restarted w/o --replSet.

Fixes an issue where temporary collections would be dropped after a
replica set member was restarted as a stand-alone mongod.

(cherry picked from commit 43e9c303c08f73b56490b662b3d11988cafafdf4)
Branch: v3.2
https://github.com/mongodb/mongo/commit/a08c37500816cae71a366570d8caebf157887f63

Comment by Githook User [ 27/Jan/17 ]

Author:

{u'username': u'visemet', u'name': u'Max Hirschhorn', u'email': u'max.hirschhorn@mongodb.com'}

Message: SERVER-26741 Retain temp collections when node restarted w/o --replSet.

Fixes an issue where temporary collections would be dropped after a
replica set member was restarted as a stand-alone mongod.
Branch: master
https://github.com/mongodb/mongo/commit/43e9c303c08f73b56490b662b3d11988cafafdf4

Comment by Eric Milkie [ 24/Oct/16 ]

I believe this can happen with any temp collections, including ones generated by map/reduce.

Generated at Thu Feb 08 04:13:04 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.