[SERVER-13512] mr_drop.js is flakey when run in parallel with other tests Created: 08/Apr/14  Updated: 11/Jul/16  Resolved: 14/Apr/14

Status: Closed
Project: Core Server
Component/s: Testing Infrastructure
Affects Version/s: 2.6.0
Fix Version/s: 2.6.1, 2.7.0

Type: Bug Priority: Major - P3
Reporter: Matt Dannenberg Assignee: Matt Dannenberg
Resolution: Done Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Related
related to SERVER-10104 mr_drop.js (via parallel/basicPlus.js... Closed
related to SERVER-10598 mr_drop.js (via parallel/basic.js) is... Closed
related to SERVER-13262 mr_drop.js can fail when its internal... Closed
Operating System: ALL
Backport Completed:
Participants:
Linked BF Score: 0

 Description   

A few fixes have been added, but none of them have fully fixed it. At this point, it should be moved into noPassthrough.



 Comments   
Comment by Githook User [ 16/Apr/14 ]

Author:

{u'username': u'dannenberg', u'name': u'matt dannenberg', u'email': u'matt.dannenberg@10gen.com'}

Message: SERVER-13512 add mr_drop.js to the skipTests in parallelTester.js
(cherry picked from commit 9ca0f4423561d2c615f4ae588068e6104794b7ee)
Branch: v2.6
https://github.com/mongodb/mongo/commit/9d7f0555fcf2180ef87995c0a054da0c064cdf9d

Comment by Githook User [ 14/Apr/14 ]

Author:

{u'username': u'dannenberg', u'name': u'matt dannenberg', u'email': u'matt.dannenberg@10gen.com'}

Message: SERVER-13512 add mr_drop.js to the skipTests in parallelTester.js
Branch: master
https://github.com/mongodb/mongo/commit/9ca0f4423561d2c615f4ae588068e6104794b7ee

Comment by Matt Dannenberg [ 08/Apr/14 ]

We believe that another test is taking a lock which causes mapreduce to block. Then once the lock is released, the parallelShell's drop runs before mapreduce (since the two second sleep has ended). When mapreduce goes to get the collection, the collection no longer exists causing mapreduce to fail with "ns doesn't exist"

Comment by Eric Milkie [ 08/Apr/14 ]

Do we understand why it is flaky? Is it due to a coding bug, or something else?

Comment by Eric Milkie [ 08/Apr/14 ]

For what reason(s) is it flaky?

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