[SERVER-56723] Cluster time keys refresh interval doesn't back off on consecutive errors Created: 06/May/21  Updated: 06/Dec/22  Resolved: 06/May/21

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

Type: Bug Priority: Major - P3
Reporter: Jack Mulrow Assignee: [DO NOT USE] Backlog - Sharding NYC
Resolution: Duplicate Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Assigned Teams:
Sharding NYC
Operating System: ALL
Participants:

 Description   

When refreshing cluster time keys, if an error occurs, the next refresh is meant to happen in 200ms * the number of consecutive errors, with a max interval of 10 minutes. The error count is set to 0 at the beginning of the while loop where retries happen though, so it can never be greater than 1, meaning the intended back off logic never applies and the interval is always 200ms.



 Comments   
Comment by Jack Mulrow [ 06/May/21 ]

Accidentally created SERVER-56722 twice.

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