[OAK-10190] Reusing Azure segment container hangs when primary location is not available

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Fix Version/s: 1.52.0
• Component/s: segment-azure
• Assignee: Andrei Dulceanu
• Reporter: Andrei Dulceanu
• Created: 14/Apr/23 14:52
• Updated: 15/May/23 16:54
• Resolved: 14/Apr/23 15:08

Description

When access to the secondary Azure blobstore service endpoint in Oak segment node store is enabled (see OAK-10050), re-using the Azure segment container hangs if the primary location is not available.

This happens because the call container.createIfNotExists() always overrides the request options set and goes to primary location only, since that is the only one allowing write access (in case the container needs to be created).

Issue Links

• links to: GitHub Pull Request #898