[SERVER-25829] Don't run killop.js in mmapv1 sharding_jscore_passthrough suite Created: 26/Aug/16  Updated: 06/Dec/22  Resolved: 31/Aug/16

Status: Closed
Project: Core Server
Component/s: Sharding
Affects Version/s: None
Fix Version/s: 3.3.14

Type: Task Priority: Major - P3
Reporter: Spencer Brody (Inactive) Assignee: [DO NOT USE] Backlog - Sharding Team
Resolution: Done Votes: 0
Labels: bkp
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Backports
Depends
Related
related to SERVER-10747 $where operator can block all other o... Backlog
related to SERVER-5326 Restructure MMAPV1 journaling to not ... Closed
Assigned Teams:
Sharding
Backwards Compatibility: Fully Compatible
Backport Requested:
v3.2
Sprint: Sharding 2016-09-19
Participants:
Linked BF Score: 0

 Description   

This test sometimes fails due to a conflict between the mmapv1 journal lock, setShardVersion, and one of the $where count commands that the test starts.



 Comments   
Comment by Githook User [ 31/Aug/16 ]

Author:

{u'username': u'stbrody', u'name': u'Spencer T Brody', u'email': u'spencer@mongodb.com'}

Message: SERVER-25829 Skip killop.js on sharding_jscore_passthrough with mmapv1 storage engine
Branch: master
https://github.com/mongodb/mongo/commit/4a3f671a1178ecf9769e6eeef05a74ea4f4765b5

Generated at Thu Feb 08 04:10:20 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.