OAK-12039 Treat transient client-side exceptions as recoverable in AzureRepositoryLock

[smiroslav]

https://issues.apache.org/jira/browse/OAK-12039

[ierandra]

I think the fix should also be added to V8 implementation.

[smiroslav]

I have changed the test to cause TimeoutException instead of mocking it.

[smiroslav]

I think the fix should also be added to V8 implementation.

@ierandra will address it in a separate PR

[smiroslav]

I decided not to update reactor-core, as the Azure documentation advises against using a version with a different major or minor version than the one specified in the Azure SDK dependencies.
Azure SDK v12 version should be updated, but I would not do that in this PR.

https://learn.microsoft.com/en-us/azure/developer/java/sdk/troubleshooting-dependency-version-conflict#understand-compatible-dependency-versions
https://github.com/reactor/.github/blob/main/SUPPORT.adoc#our-policy-on-deprecations

Instead, IllegalStateException is treated as recoverable.

[smiroslav]

I think the fix should also be added to V8 implementation.

@ierandra will address it in a separate PR

The AzureRepositoryLockV8 is already correctly handling client-side timeout exceptions in the correct way:
#2667

[ierandra]

@smiroslav

The AzureRepositoryLockV8 is already correctly handling client-side timeout exceptions in the correct way:

that is very strange because when we did the analysis we observe the same issue for customers running on v8

[smiroslav]

@ierandra, looking at the code, all exceptions that happen in AzureRepositoryLockV8#refreshLease should be logged.

Do you perhaps have the stacktrace?

I suggest we move the discussion for v8 to the JIRA or #2667.

[jsedding]

I decided not to update reactor-core ...

I hope you're still merging the rest of the PR, because eventually we will update azure and reactor 🙂