[SERVER-4496] boost::lock_error on mongod shutdown Created: 15/Dec/11 Updated: 11/Jul/16 Resolved: 16/Apr/12 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Storage |
| Affects Version/s: | None |
| Fix Version/s: | 2.1.1 |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Aaron Staple | Assignee: | Dwight Merriman |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Operating System: | ALL |
| Participants: |
| Description |
|
Saw this after ctrl-c'ing mongod after doing some testing: Wed Dec 14 18:56:53 dbexit: really exiting now Wed Dec 14 18:56:53 Backtrace: |
| Comments |
| Comment by auto [ 19/Dec/11 ] |
|
Author: {u'login': u'dwight', u'name': u'Dwight', u'email': u'dwight@10gen.com'}Message: |
| Comment by Dwight Merriman [ 19/Dec/11 ] |
|
_groupCommitWithLimitedLocks releases its read lock early; that was the thinking with the groupmutex. however, i think you are right about writeexcluder. i'll do that too. the groupmutex thing is probably not the problem as it is unlikely there is anything to be committed at that point anyway. it may be worth keeping the fix though as it is more correct that would be relying on assumptions. |
| Comment by Dwight Merriman [ 18/Dec/11 ] |
|
lmk if that helps or if it reads to you that it will fix |
| Comment by auto [ 18/Dec/11 ] |
|
Author: {u'login': u'dwight', u'name': u'dwight', u'email': u'dwight@10gen.com'}Message: |
| Comment by Aaron Staple [ 17/Dec/11 ] |
|
Just saw it again. |
| Comment by Aaron Staple [ 15/Dec/11 ] |
|
Before I saw that I had just run our jstests against the mongod that produced this stack trace. |