[OAK-4770] Missing exception handling in ClusterNodeInfo.renewLease()

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Fix Version/s: 1.4.10, 1.5.10, 1.6.0
• Component/s: core, documentmk
• Labels: resilience
• Epic Link: DocumentMK resilience
• Assignee: Marcel Reutegger
• Reporter: Marcel Reutegger
• Created: 07/Sep/16 13:04
• Updated: 16/Feb/21 09:53
• Resolved: 13/Sep/16 08:24

Description

ClusterNodeInfo.renewLease() does not handle a potential DocumentStoreException on findAndModify(). This may leave previousLeaseEndTime in an inconsistent state and a subsequent renewLease() call then considers the lease timed out.

Issue Links

• is duplicated by: OAK-4739 lease: immediate renew after long renew call
• is related to: OAK-4779 ClusterNodeInfo may renew lease while recovery is running
• is related to: OAK-4739 lease: immediate renew after long renew call
• is related to: OAK-4792 Replace usage of AssertionError in ClusterNodeInfo