[SERVER-28572] Update test case to use valid custom WiredTiger configuration values Created: 31/Mar/17  Updated: 15/Aug/17  Resolved: 03/Apr/17

Status: Closed
Project: Core Server
Component/s: Storage
Affects Version/s: None
Fix Version/s: 3.2.13, 3.4.4, 3.5.6

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

Issue Links:
Backports
Backwards Compatibility: Fully Compatible
Operating System: ALL
Backport Requested:
v3.4, v3.2
Sprint: Storage 2017-04-17
Participants:

 Description   

The noPassthrough/wt_index_option_defaults.js test sets the WiredTiger table configuration split_pct to values less than 50. A recent change in WT-2439 put a lower bound of 50 on that configuration option. The goal of the test case is to ensure custom configuration values appear where expected, the actual values aren't material. It should be updated to use a different set of values.



 Comments   
Comment by Githook User [ 03/Apr/17 ]

Author:

{u'username': u'agorrod', u'name': u'Alex Gorrod', u'email': u'alexander.gorrod@mongodb.com'}

Message: SERVER-28572 Change a js test to comply with configuration bounds
(cherry picked from commit 08d29c36403608802c45375277f88c7fcaf708e0)

Change a js test because WiredTiger is changing the range of values possible for split_pct
which this test happens to use as a way to test custom configuration visibility.
Branch: v3.2
https://github.com/mongodb/mongo/commit/3dd42615d7f125a9e5b5779851942d983638a526

Comment by Githook User [ 03/Apr/17 ]

Author:

{u'username': u'agorrod', u'name': u'Alex Gorrod', u'email': u'alexander.gorrod@mongodb.com'}

Message: SERVER-28572 Change a js test to comply with configuration bounds

(cherry picked from commit 08d29c36403608802c45375277f88c7fcaf708e0)

Change a js test because WiredTiger is changing the range of values possible for split_pct
which this test happens to use as a way to test custom configuration visibility.
Branch: v3.4
https://github.com/mongodb/mongo/commit/bb4f7cbe5a09f42df56d8284655eaea412e2459c

Comment by Githook User [ 31/Mar/17 ]

Author:

{u'username': u'agorrod', u'name': u'Alex Gorrod', u'email': u'alexander.gorrod@mongodb.com'}

Message: SERVER-28572

Change a js test because WiredTiger is changing the range of values possible for split_pct
which this test happens to use as a way to test custom configuration visibility.
Branch: master
https://github.com/mongodb/mongo/commit/08d29c36403608802c45375277f88c7fcaf708e0

Comment by Alexander Gorrod [ 31/Mar/17 ]

The change in WT-2439 is destined to be backported into MongoDB 3.2 and 3.4 - as such this test change needs to be backported as well.

Comment by Alexander Gorrod [ 31/Mar/17 ]

The test case uses the following values:

 31     // Use different values for the same configuration string key to test that index-specific
 32     // options override collection-wide options, and that collection-wide options override
 33     // system-wide options.
 34     var systemWideConfigString = 'split_pct=25,';
 35     var collectionWideConfigString = 'split_pct=30,';
 36     var indexSpecificConfigString = 'split_pct=35,';

They could safely be updated to 70, 75 and 80.

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