[SERVER-23782] make Shard::_runCommand and Shard::_exhaustiveFindOnConfig take a timeout argument Created: 18/Apr/16  Updated: 06/Dec/22  Resolved: 21/Apr/16

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

Type: Task Priority: Major - P3
Reporter: Esha Maharishi (Inactive) Assignee: [DO NOT USE] Backlog - Sharding Team
Resolution: Won't Fix Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Related
is related to SERVER-23784 Don't use 30 second network timeout o... Closed
Assigned Teams:
Sharding
Participants:

 Description   

Currently, kConfigCommandTimeout (30 seconds) is always used.



 Comments   
Comment by Spencer Brody (Inactive) [ 18/Apr/16 ]

Hmm... I wonder if this could be related to SERVER-23487 - we're forcing a 30 second maxTimeMS on any operation run on a shard through the ShardRegistry, even when it might make sense for that operation to take more than 30 seconds.

Generated at Thu Feb 08 04:04:28 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.