[SERVER-11419] dur/closeall.js failing on RHEL 5.7 Created: 28/Oct/13 Updated: 11/Jul/16 Resolved: 31/Oct/13 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Build, Testing Infrastructure |
| Affects Version/s: | None |
| Fix Version/s: | 2.5.4 |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | sam.helman@10gen.com | Assignee: | hari.khalsa@10gen.com |
| Resolution: | Done | Votes: | 0 |
| Labels: | build-failure, buildbot | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Environment: |
RHEL 5.7 64-bit |
||
| Issue Links: |
|
||||||||
| Operating System: | ALL | ||||||||
| Participants: | |||||||||
| Description |
|
buildlogger link: Failure synopsis:
|
| Comments |
| Comment by auto [ 31/Oct/13 ] |
|
Author: {u'username': u'hkhalsa', u'name': u'Hari Khalsa', u'email': u'hkhalsa@10gen.com'}Message: |
| Comment by hari.khalsa@10gen.com [ 29/Oct/13 ] |
|
kangas eliot Yes, this is a lifecycle thing. We invalidate all cursors open on the DB then assert that there are no cursors. Previously we'd just delete the cursors. However, I tag active (ie, a thread is using it in clientcursor or somebody doesn't have a cursorid for it but there is a thread using it) cursors as 'dead' to avoid having to deal with yielding being self-deleting. We could perhaps move these cursors to a zombie state, or not assert, or assert any cursors are dead, or something else? I am reluctant to have yielding imply self-deletion. |