[SERVER-8589] drop2.js failing under auth Created: 15/Feb/13 Updated: 11/Jul/16 Resolved: 15/Feb/13 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Testing Infrastructure |
| Affects Version/s: | 2.4.0-rc0 |
| Fix Version/s: | 2.4.0-rc1 |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Eric Milkie | Assignee: | Eric Milkie |
| Resolution: | Done | Votes: | 0 |
| Labels: | buildbot | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Operating System: | ALL |
| Participants: |
| Description |
|
drop2.js tests the ability to drop a collection while a long running read operation is occurring on that same collection. Unfortunately, it does this using a count given a "$where: while(1) sleep;" operation. Normally, this works okay, but if you are using auth, an extra read lock is necessary to authenticate the operations. This extra read lock in combination with the journal thread doing a commit may deadlock against the read lock held by the count query. |
| Comments |
| Comment by Randolph Tan [ 18/Apr/13 ] |
|
Note: last commit was actually for |
| Comment by auto [ 18/Apr/13 ] |
|
Author: {u'date': u'2013-04-18T15:46:45Z', u'name': u'Randolph Tan', u'email': u'randolph@10gen.com'}Message: Made sure to increment the counter after the event happened, not before. |
| Comment by auto [ 15/Feb/13 ] |
|
Author: {u'date': u'2013-02-15T18:35:32Z', u'name': u'Eric Milkie', u'email': u'milkie@10gen.com'}Message: |