[SERVER-79482] Tenant migration/merge and split passthrough should support timeseries workload. Created: 28/Jul/23  Updated: 29/Oct/23  Resolved: 28/Aug/23

Status: Closed
Project: Core Server
Component/s: None
Affects Version/s: None
Fix Version/s: 7.1.0-rc0

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
depends on SERVER-80301 View/Timeseries recreated on a droppe... Closed
Related
is related to SERVER-69168 Clean up time series test tagging and... Closed
Assigned Teams:
Storage Execution NAMER
Backwards Compatibility: Fully Compatible
Operating System: ALL
Backport Requested:
v7.0
Sprint: Execution NAMR Team 2023-08-21, Execution NAMR Team 2023-09-04
Participants:

 Description   

Although Serverless supports timeseries, we have currently blacklisted all timeseries workloads in tenant migration/merge and split passthroughs using the requires_timeseries tag. As a result, there is no test coverage for the Serverless migration + timeseries combo. We should re-enable Serverless migration passthrough suites to support timeseries workloads. If this is not possible, the Serverless team would appreciate an explanation regarding:

1) Why enabling it is not feasible?
2) Whether it is possible to enable a subset of timeseries core tests or not?



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

Author:

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

Message: SERVER-79482 Run time-series workloads on tenant migration/merge and split passthrough suites
Branch: master
https://github.com/mongodb/mongo/commit/4ad74cfe04beba5240cd8b5e0305023022d5398a

Comment by Suganthi Mani [ 28/Jul/23 ]

Reposting dan.larkin-york@mongodb.com slack response 

Going way back, before SERVER-69168, nearly every test in jstests/core/timeseries was tagged with tenant_migration_incompatible, but new tests were sometimes not tagged the same way as existing tests for necessary exclusions (tenant migrations among others), and we would get intermittent, hard-to-reproduce failures.It's not 100% clear to me why we initially had those tests marked as tenant migration incompatible, and it's possible it's not necessary any more. If you want to try kicking off a patch (or few) without the requires_timeseries exclusion for tenant migration passthroughs and see what breaks, that sounds reasonable to me. If it turns out there's a specific subset of tests that are currently incompatible, then we can just tag those tests instead of the blanket exclusion. (Similarly, we have several tests that aren't compatible with stepdowns, so those are tagged, and we're planning to move those to noPassthrough in a future ticket.) If it looks like a more general test compatibility problem (not limited to small set of tests), then that's worth investigating sooner rather than later.

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