[SERVER-14475] Race conditions in clean shutdown Created: 07/Jul/14 Updated: 11/Jul/16 Resolved: 25/Jul/14 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Stability |
| Affects Version/s: | None |
| Fix Version/s: | 2.7.5 |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Mathias Stearn | Assignee: | Kaloian Manassiev |
| Resolution: | Done | Votes: | 0 |
| Labels: | cap-ticket-needed | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||
| Operating System: | ALL | ||||
| Participants: | |||||
| Description |
|
inShutdown() becomes true rather late in the shutdown procedure. Among potentially other issues, it comes after we close our listening sockets which can trigger fatal assertion 16727. I think inShutdown must become true before we begin any shutdown-related activities. This may require decoupling it from the numExitCalls counter. There's also a race condition with the listener thread exiting before the _exit call from a previous exitClean call completing, which causes the server to exit with return code 48 (EXIT_NET_ERROR). |
| Comments |
| Comment by Githook User [ 25/Jul/14 ] |
|
Author: {u'username': u'kaloianm', u'name': u'Kaloian Manassiev', u'email': u'kaloian.manassiev@mongodb.com'}Message: |
| Comment by Githook User [ 24/Jul/14 ] |
|
Author: {u'username': u'kaloianm', u'name': u'Kaloian Manassiev', u'email': u'kaloian.manassiev@mongodb.com'}Message: |
| Comment by Githook User [ 18/Jul/14 ] |
|
Author: {u'username': u'kaloianm', u'name': u'Kaloian Manassiev', u'email': u'kaloian.manassiev@mongodb.com'}Message: |