[SERVER-24963] Concurrent collection.drop() and system.indexes.count() can trigger an fassert Created: 08/Jul/16 Updated: 05/Apr/17 Resolved: 28/Nov/16 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Index Maintenance, MMAPv1 |
| Affects Version/s: | 3.2.7 |
| Fix Version/s: | 3.2.13, 3.4.3, 3.5.1 |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Robert Guo (Inactive) | Assignee: | Geert Bosch |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| 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: | Integration 2016-10-10, Integration 2016-10-31, Storage 2016-11-21, Storage 2016-12-12 | ||||||||||||||||
| Participants: | |||||||||||||||||
| Linked BF Score: | 0 | ||||||||||||||||
| Description |
|
Doing a collection drop and a count on system.indexes can trigger an fassert. I was able to repro this on an mmapv1 2 node replica set but not an 1 node replica set. Affects 3.2 and master backtrace:
|
| Comments |
| Comment by Githook User [ 03/Feb/17 ] |
|
Author: {u'username': u'GeertBosch', u'name': u'Geert Bosch', u'email': u'geert@mongodb.com'}Message: (cherry picked from commit 647ebfac9ebf1c5fc431a2ba813bf9c97b9bdab9) |
| Comment by Githook User [ 02/Feb/17 ] |
|
Author: {u'username': u'GeertBosch', u'name': u'Geert Bosch', u'email': u'geert@mongodb.com'}Message: (cherry picked from commit 647ebfac9ebf1c5fc431a2ba813bf9c97b9bdab9) Conflicts: |
| Comment by Githook User [ 28/Nov/16 ] |
|
Author: {u'username': u'GeertBosch', u'name': u'Geert Bosch', u'email': u'geert@mongodb.com'}Message: |
| Comment by Robert Guo (Inactive) [ 12/Jul/16 ] |
|
schwerin I haven't had luck reproing this on 3.0.10... |
| Comment by Andy Schwerin [ 12/Jul/16 ] |
|
Does this affect 3.0? robert.guo |