[OAK-9914] Starting Oak with Azure persistence in read-only mode while another Oak process is running will initiate repo recovery

• Type: New Feature
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 1.44.0
• Fix Version/s: 1.46.0
• Component/s: segment-azure
• Assignee: Julian Sedding
• Reporter: Miroslav Smiljanic
• Created: 30/Aug/22 16:27
• Updated: 21/Dec/22 03:39
• Resolved: 02/Sep/22 15:40

Description

The sequence of events:

1. Oak process with read/write file store utilizing Azure persistence is already running 
2. New Oak process is starting up, with read-only file store using Azure persistence and the same storage account and container like the previous Oak process
   1. New Oak process starts recovery procedure for the last tar directory that is not closed, and that has an impact on the startup time 

Scenario presented in the attached test case:

OAK-9914_test.patch 

Issue Links

• causes: OAK-9927 Building file store with azure caching persistence fails if another process is using azure persistence with the same azure directory
• causes: OAK-10022 ReadOnlyFileStore#collectBlobReferences throws NullPointerException if azure blob with binary references is missing in the tar directory
• links to: GitHub Pull Request #685
• links to: GitHub Pull Request #686