[SERVER-83172] Handle intermittent validate command failure in shard merge passthrough suites due to timeseries uncompressed bucket workload. Created: 13/Nov/23  Updated: 28/Nov/23  Resolved: 15/Nov/23

Status: Closed
Project: Core Server
Component/s: None
Affects Version/s: None
Fix Version/s: 7.3.0-rc0, 7.2.0-rc2

Type: Bug Priority: Major - P3
Reporter: Suganthi Mani Assignee: Gregory Wlodarek
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Backports
Depends
Assigned Teams:
Storage Execution
Backwards Compatibility: Fully Compatible
Operating System: ALL
Backport Requested:
v7.2, v7.1
Sprint: Execution Team 2023-11-27
Participants:
Linked BF Score: 15

 Description   

There are some jscore timeseries tests (timeseries_create.js) that insert uncompressed buckets directly into the system.bucket.* collection, which can cause the collection validation hook to fail in shard merge passthrough suites on feature flags build variant. That's because we run the validate command with enforceTimeseriesBucketsAreAlwaysCompressed set to true when featureFlagTimeseriesAlwaysUseCompressedBuckets is enabled.

timeseries_reopened_bucket_insert.js, which also inserts uncompressed buckets directly into the system.bucket.* collection, faced a similar BF issue. But, we fixed the problem by tagging the test as tenant_migration_incompatible. I don't think that's a correct way to fix this problem.

Those problematic tests not only does uncompressed bucket testing but also perform compressed bucket testing. Thus, blacklisting those tests would result in a loss of coverage for those compressed bucket testing in the merge passthrough suites. So, I recommend running the merge passthrough suites with skipEnforceTimeseriesBucketsAreAlwaysCompressedOnValidate. Once featureFlagTimeseriesAlwaysUseCompressedBuckets is enabled by default by defauly(targeted for 7.3), I anticipate that PM-3055 will update all jscore tests to remove explicit uncompressed bucket sequence testing.

This is problem also applies to tenant migration and shard split passthrough suites



 Comments   
Comment by Githook User [ 28/Nov/23 ]

Author:

{'name': 'Gregory Wlodarek', 'email': 'gregory.wlodarek@mongodb.com', 'username': 'GWlodarek'}

Message: SERVER-83172 Update timeseries_create.js to insert compressed buckets

(cherry picked from commit 566ad4caee051e16cffe7dc84cf4a615de3b6b59)
Branch: v7.2
https://github.com/mongodb/mongo/commit/50d8c3b05466dcd509cfe0e847f696e2e94ed5c6

Comment by Githook User [ 15/Nov/23 ]

Author:

{'name': 'Gregory Wlodarek', 'email': 'gregory.wlodarek@mongodb.com', 'username': 'GWlodarek'}

Message: SERVER-83172 Update timeseries_create.js to insert compressed buckets
Branch: master
https://github.com/mongodb/mongo/commit/566ad4caee051e16cffe7dc84cf4a615de3b6b59

Generated at Thu Feb 08 06:51:26 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.