[SERVER-83493] Modify clusterwide_ops_with_add_remove_shards.js to avoid test timeout failures due to slow execution Created: 21/Nov/23  Updated: 24/Nov/23  Resolved: 23/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: Paolo Polato Assignee: Paolo Polato
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
Related
related to SERVER-82901 Investigate why addShard can fail wit... Closed
Backwards Compatibility: Fully Compatible
Sprint: CAR Team 2023-11-27
Participants:
Linked BF Score: 57

 Description   

SERVER-81974 introduced the execution of a setClusterParameter command as part of both addShard and removeShard, causing a slightly increased execution time of a user request when the cluster transitions from/into a single shard topology when it gets committed.

This overhead is now causing sporadic failures of the clusterwide_ops_with_add_remove_shards.js test, which heavily stresses this execution path and may go beyond the Evergreen timeout when run in slower variants.



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

Author:

{'name': 'Paolo Polato', 'email': 'paolo.polato@mongodb.com', 'username': 'ppolato'}

Message: SERVER-83493 Reduce the FSM threadCount to improve the exe time of clusterwide_ops_with_add_remove_shards.js
Branch: master
https://github.com/mongodb/mongo/commit/7d7fdaf385fe0b9bfddca4b0f141a085013a4c1c

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