[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.
To fix this, I am adding drop2.js to the auth testing blacklist.



 Comments   
Comment by Randolph Tan [ 18/Apr/13 ]

Note: last commit was actually for SERVER-8598.

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: SERVER-8589 Fixed race in range_deleter_test

Made sure to increment the counter after the event happened, not before.
Branch: master
https://github.com/mongodb/mongo/commit/8720e07600694c4390faab186ad5da8bdbe49a3a

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: SERVER-8589 disable drop2.js for auth testing
Branch: master
https://github.com/mongodb/mongo/commit/fccd00cad578064cbab4ef0c55d3527ed7ef1436

Generated at Thu Feb 08 03:17:50 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.