[SERVER-56722] Cluster time keys refresh interval doesn't back off on consecutive errors Created: 06/May/21  Updated: 29/Oct/23  Resolved: 10/Jun/21

Status: Closed
Project: Core Server
Component/s: None
Affects Version/s: None
Fix Version/s: 5.0.0-rc2, 5.1.0-rc0

Type: Bug Priority: Major - P3
Reporter: Jack Mulrow Assignee: Jack Mulrow
Resolution: Fixed Votes: 1
Labels: neweng
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Backports
Related
is related to SERVER-49393 KeysCollectionManager should not sile... Closed
Backwards Compatibility: Fully Compatible
Operating System: ALL
Backport Requested:
v5.0, v4.4, v4.2, v4.0
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 Vivian Ge (Inactive) [ 06/Oct/21 ]

Updating the fixversion since branching activities occurred yesterday. This ticket will be in rc0 when it’s been triggered. For more active release information, please keep an eye on #server-release. Thank you!

Comment by Githook User [ 10/Jun/21 ]

Author:

{'name': 'Jack Mulrow', 'email': 'jack.mulrow@mongodb.com', 'username': 'jsmulrow'}

Message: SERVER-56722 Fix cluster time key refresh backoff logic

(cherry picked from commit e712fd4bda1a1511506dc7481e03ed48a146cc8e)
Branch: v5.0
https://github.com/mongodb/mongo/commit/29cb0880aee03a3db187872e047164b2bd3b86c9

Comment by Githook User [ 09/Jun/21 ]

Author:

{'name': 'Jack Mulrow', 'email': 'jack.mulrow@mongodb.com', 'username': 'jsmulrow'}

Message: SERVER-56722 Fix cluster time key refresh backoff logic
Branch: master
https://github.com/mongodb/mongo/commit/e712fd4bda1a1511506dc7481e03ed48a146cc8e

Comment by Jack Mulrow [ 03/Jun/21 ]

Increasing the priority because with the changes from SERVER-49393, the failure to back off on errors leads to log spam in uninitialized replica sets.

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