[SERVER-83670] Avoid using too long tenant prefixed db name in FSM multitenancy test Created: 28/Nov/23  Updated: 01/Dec/23  Resolved: 30/Nov/23

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

Type: Task Priority: Major - P3
Reporter: Sophia Tan Assignee: Sophia Tan
Resolution: Fixed Votes: 0
Labels: ntdi_must_have
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Issue split
split from SERVER-74910 Create concurrency test suite that ru... Closed
Backwards Compatibility: Fully Compatible
Sprint: Service Arch 2023-12-11
Participants:
Story Points: 1

 Description   

As the tenant prefix string length is 24, the tenant prefixed db name of some fsm_workloads test will exceed the max db name length allowed by mongod. We need to avoid using too long tenant prefixed db name in FSM multitenancy test. 



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

Author:

{'name': 'Sophia Tan', 'email': 'sophia_tll@hotmail.com', 'username': 'sophiatll'}

Message: SERVER-83670 Avoid using too long tenant prefixed db name in FSM multitenancy test
Branch: master
https://github.com/mongodb/mongo/commit/f2cfc2b9051ea2b27b3cb0bec747ca5416801893

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