[OAK-10006] AzurePersistence can still write segments after having lost lease to another instance

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 1.44.0, 1.58.0
• Fix Version/s: 1.60.0
• Component/s: segment-azure, segment-tar
• Assignee: Miroslav Smiljanic
• Reporter: Carlo Jelmini
• Created: 18/Nov/22 12:04
• Updated: 16/Feb/24 09:47
• Resolved: 21/Nov/23 13:13

Description

If the SegmentWriteQueue have pending writes while AzurePersistence is unable to renew the lease (both likely caused by connection problems with Azure), and another Oak instance starts and acquire the lease, then the first Oak instance may still be able to write segments to Azure, corrupting the repository.

We need to make sure no writes can happen if the lease has been lost to another instance.

Issue Links

• causes: OAK-10652 Repository writes in SegmentStoreMigrator blocked when migrating to Azure segment store
• links to: GitHub PR #1204
• links to: GitHub Pull Request #760