Direct Package Upgrade: Fixes Cosmos.Direct
Package to 3.36.0
#4687
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Pull Request Template
Description
This PR is bumping up the
Cosmos.Direct
package version from3.35.0
to3.36.0
, which includes the below changes:ReadsMultipleReplicas
andReadPrimary
involved in Strong/Bounded quorum to make sure that the responses are treated as errors and propagated above.PartitionKey.None.GetHashCode()
throwsNullReferenceException
.GoneAndRetryWithRequestRetryPolicy
- Refactors policy to throw503
Service Unavailable when a410
Gone Exception with Sub-Status code 1022 is Received.Understanding Gone Exception (Status Code: 410) with Lease Not Found (Sub Status Code: 1022).
Background: In general
410/1022
is used as a signal to indicate that a region is not part of the dynamic quorum - meaning in global strong with dynamic quorum all reads from the secondary region kicked out of the quorum will return410/1022
.410/LeaseNotFound
- the client will then retry locally for up-to60
seconds (for global strong) and up-to30
seconds (for others) (catch-all 410 retry like for 410/0 or connectivity related 410) for any.Instead the
410/LeaseNotFound(1022)
should be mapped immediately to a503
to allow the cross-regional retry to happen as quickly as possible. Retrying in the next preferred region like usual for reads is acceptable. This has been taken care in theCosmos.Direct
release3.36.0
and this PR is upgrading theCosmos.Direct
version to3.36.0
to reflect the change.Type of change
Please delete options that are not relevant.
Closing issues
To automatically close an issue: closes #4390