[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: |
|
||||||||||||||||||||
| Backwards Compatibility: | Fully Compatible | ||||||||||||||||||||
| Operating System: | ALL | ||||||||||||||||||||
| Backport Requested: |
v3.4, v3.2
|
||||||||||||||||||||
| Sprint: | TIG 2017-02-13 | ||||||||||||||||||||
| Participants: | |||||||||||||||||||||
| Case: | (copied to CRM) | ||||||||||||||||||||
| 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 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.
|
| 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: Fixes an issue where temporary collections would be dropped after a (cherry picked from commit 43e9c303c08f73b56490b662b3d11988cafafdf4) |
| 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: Fixes an issue where temporary collections would be dropped after a (cherry picked from commit 43e9c303c08f73b56490b662b3d11988cafafdf4) |
| 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: Fixes an issue where temporary collections would be dropped after a |
| Comment by Eric Milkie [ 24/Oct/16 ] |
|
I believe this can happen with any temp collections, including ones generated by map/reduce. |