[SERVER-16205] exiting with SIGINT during WT initialization can fassert Created: 17/Nov/14 Updated: 11/Jul/16 Resolved: 19/Nov/14 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Storage |
| Affects Version/s: | None |
| Fix Version/s: | 2.8.0-rc1 |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Eric Milkie | Assignee: | Eric Milkie |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Operating System: | ALL |
| Participants: |
| Description |
|
Because we do most of the initialization work in finishInit() rather than the constructor, it is possible to call exitCleanly() when the global storage engine pointer is valid but _initialized is still false. |
| Comments |
| Comment by Githook User [ 19/Nov/14 ] |
|
Author: {u'username': u'milkie', u'name': u'Eric Milkie', u'email': u'milkie@10gen.com'}Message: |