[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: |
|
||||||||||||
| 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: |
| Comment by Githook User [ 20/Oct/17 ] |
|
Author: {'email': 'dianna.hohensee@10gen.com', 'name': 'Dianna Hohensee', 'username': 'DiannaHohensee'}Message: Revert " This reverts commit 258691ffb9ee561c48e897e1df6a1bc10ae376d6. |
| Comment by Githook User [ 20/Oct/17 ] |
|
Author: {'email': 'dianna.hohensee@10gen.com', 'name': 'Dianna Hohensee', 'username': 'DiannaHohensee'}Message: |
| Comment by Dianna Hohensee (Inactive) [ 18/Oct/17 ] |
|
Given how many suites are failing, a NOT_SHARDING test tag might be nice. |