[SERVER-64233] shard split jstest case should not depend on maxTimeMS to prove a tenant access blocker is installed Created: 04/Mar/22  Updated: 29/Oct/23  Resolved: 28/Mar/22

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

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

Issue Links:
Depends
Backwards Compatibility: Fully Compatible
Operating System: ALL
Sprint: Server Serverless 2022-03-07, Server Serverless 2022-03-21, Server Serverless 2022-04-04
Participants:
Linked BF Score: 19

 Description   

Currently, shard_split_tenant_access_blocking.js depends on the maxTimeMS to prove a tenant access blocker is installed by attempting a write. But, even if we get time out response, we still cannot say it's 100% caused by a tenant access blocker. 

In this ticket, mtab.numBlockedWrites will be used the same purpose as the create_indexes_with_tenant_migration.js does.



 Comments   
Comment by Githook User [ 25/Mar/22 ]

Author:

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

Message: SERVER-64233 shard split jstest case should not depend on maxTimeMS to prove a tenant access blocker is installed
Branch: master
https://github.com/mongodb/mongo/commit/f88d0d5e7dce55613fdd7085118731de4a92ba91

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