[SERVER-31615] Blacklist queryoptimizer3.js from all sharding passthrough suites Created: 18/Oct/17  Updated: 30/Oct/23  Resolved: 20/Oct/17

Status: Closed
Project: Core Server
Component/s: Sharding
Affects Version/s: None
Fix Version/s: 3.6.0-rc1

Type: Bug Priority: Major - P3
Reporter: Dianna Hohensee (Inactive) Assignee: Dianna Hohensee (Inactive)
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
Related
related to SERVER-32567 Replace queryoptimizer3.js with FSM test Closed
Backwards Compatibility: Fully Compatible
Operating System: ALL
Sprint: Sharding 2017-10-23
Participants:
Linked BF Score: 0

 Description   

queryoptimizer3.js has a parallel thread running periodic drop collection commands. The rest of the test is performing reads and further drops. In the sharding suites, this test keeps running into LockBusy. This is because the cluster drop collection command takes distlocks, whereas the shard drop collection command does not.

Some of the failing suites: causally_consistent_jscore_passthrough_WT, sharding_jscore_passthrough_WT, sharding_jscore_op_query_passthrough_WT, sharding_jscore_passthrough_wire_ops_WT, concurrency_sharded_causal_consistency_and_balancer, sharded_collections_jscore_passthrough_WT



 Comments   
Comment by Dianna Hohensee (Inactive) [ 20/Oct/17 ]

I reverted it prematurely on build failures: the failures were due to AWS (machines running out of space) rather than the commit. Recommitted.

Comment by Githook User [ 20/Oct/17 ]

Author:

{'email': 'dianna.hohensee@10gen.com', 'name': 'Dianna Hohensee', 'username': 'DiannaHohensee'}

Message: SERVER-31615 add tag to queryoptimizer3.js so it doesn't run in sharded passthrough suites
Branch: master
https://github.com/mongodb/mongo/commit/cebd8dfd83281b224bc6bb155b134f7f12d1f37f

Comment by Githook User [ 20/Oct/17 ]

Author:

{'email': 'dianna.hohensee@10gen.com', 'name': 'Dianna Hohensee', 'username': 'DiannaHohensee'}

Message: Revert "SERVER-31615 add tag to queryoptimizer3.js so it doesn't run in sharded passthrough suites"

This reverts commit 258691ffb9ee561c48e897e1df6a1bc10ae376d6.
Branch: master
https://github.com/mongodb/mongo/commit/8abd58df5ab9799bd5d3930d6e240928e266fad5

Comment by Githook User [ 20/Oct/17 ]

Author:

{'email': 'dianna.hohensee@10gen.com', 'name': 'Dianna Hohensee', 'username': 'DiannaHohensee'}

Message: SERVER-31615 add tag to queryoptimizer3.js so it doesn't run in sharded passthrough suites
Branch: master
https://github.com/mongodb/mongo/commit/258691ffb9ee561c48e897e1df6a1bc10ae376d6

Comment by Dianna Hohensee (Inactive) [ 18/Oct/17 ]

Given how many suites are failing, a NOT_SHARDING test tag might be nice.

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