[SERVER-64050] set TemporarilyUnavailableException::kRetryBackoff higher Created: 28/Feb/22  Updated: 29/Oct/23  Resolved: 11/Mar/22

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

Type: Improvement Priority: Major - P3
Reporter: Eric Milkie Assignee: Louis Williams
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
Documented
is documented by DOCS-15168 [SERVER] set TemporarilyUnavailableEx... Closed
Related
is related to SERVER-60839 Introduce a TemporarilyUnavailable er... Closed
Backwards Compatibility: Fully Compatible
Sprint: Execution Team 2022-03-07, Execution Team 2022-03-21
Participants:

 Description   

Currently, TemporarilyUnavailableException::kRetryBackoff is set to 100 milliseconds, which doesn't seem like enough delay to give the retry of the operation a good chance to succeed. I recommend we change this value to at least 2 seconds, and keep the number of retries hardcoded at "3". Thus, with linear increasing of the delay for each retry, prior to the last retry the delay will be 6 seconds, which doesn't seem unreasonable for an overloaded system. Control of this delay server-side is important since returning a retriable error immediately with no retrying will typically result in immediate retry by the drivers with no delay.



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

Author:

{'name': 'Louis Williams', 'email': 'louis.williams@mongodb.com', 'username': 'louiswilliams'}

Message: SERVER-64050 Increase TemporarilyUnavailable retry backoff and enable by default

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