[SERVER-60578] [4.4] Use higher timeouts for config server writes in mongos_large_catalog_workloads sys perf workload Created: 08/Oct/21  Updated: 11/Jul/23  Resolved: 11/Jul/23

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

Type: Improvement Priority: Major - P3
Reporter: Jack Mulrow Assignee: Wenqin Ye
Resolution: Won't Fix Votes: 0
Labels: sharding-nyc-subteam3, sharding-nyc-test-improvements, sharding-wfbf-day
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
Related
related to SERVER-47909 Fix mongos_large_catalog_workloads Ne... Backlog
Assigned Teams:
Sharding NYC
Participants:
Linked BF Score: 0
Story Points: 1

 Description   

The sys perf workload mongos_large_catalog_workloads writes up to a million documents into config.chunks, meant to simulate metadata with very many collections. Prior to SERVER-51070, writes against the config server through a mongos would use a maxTimeMS of 30 seconds, and prior to PM-2130, if such writes weren't sent with an explicit write concern, they would use majority with a wtimeout of 30 seconds. Occasionally these timeouts are exceeded on branches that don't include those changes, in particular 4.4 and earlier. This ticket is to track using higher timeouts to avoid failures on those branches.



 Comments   
Comment by Wenqin Ye [ 11/Jul/23 ]

Closing as not worth fixing since 4.4 is almost EOL.

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