[SERVER-26377] Skip running FSM workloads that use the compact command on the LSM build variant Created: 28/Sep/16  Updated: 08/Sep/17  Resolved: 01/Feb/17

Status: Closed
Project: Core Server
Component/s: Testing Infrastructure
Affects Version/s: None
Fix Version/s: 3.4.9, 3.5.3

Type: Task Priority: Major - P3
Reporter: Max Hirschhorn Assignee: Eddie Louie
Resolution: Done Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Backports
Depends
Related
is related to WT-2523 LSM index compaction hangs after crea... Closed
Backwards Compatibility: Fully Compatible
Backport Requested:
v3.4
Sprint: TIG 2017-01-02, TIG 2017-02-13
Participants:
Linked BF Score: 0

 Description   

WT-2523 is a known hang when running the "compact" command. We should skip running the compact.js and the compact_simultaneous_padding_bytes.js FSM workloads when using WiredTiger's LSM trees.

We should disable these tests in a way that doesn't cause us to lose coverage of running the "compact" command concurrently with other operations on other storage engines. One option is to use db[this.threadCollName].stats().wiredTiger.type === "lsm" to further refine the existing storage engine checks and skip running the "compact" command altogether.



 Comments   
Comment by Githook User [ 22/Aug/17 ]

Author:

{'username': 'elouie99', 'email': 'eddie.louie@mongodb.com', 'name': 'Eddie Louie'}

Message: SERVER-26377 Skip FSM workloads that use the compact command on the LSM build variant

(cherry picked from commit 8e34979440be7d97f92c71e85a9644108ce60c68)
Branch: v3.4
https://github.com/mongodb/mongo/commit/0071856fa9018f16b40f0c7c492fd445f673060d

Comment by Githook User [ 01/Feb/17 ]

Author:

{u'username': u'elouie99', u'name': u'Eddie Louie', u'email': u'eddie.louie@mongodb.com'}

Message: SERVER-26377 Skip FSM workloads that use the compact command on the LSM build variant
Branch: master
https://github.com/mongodb/mongo/commit/8e34979440be7d97f92c71e85a9644108ce60c68

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