Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Fix for bulk operations incorrect routing on split #21420

Merged
merged 4 commits into from
May 17, 2021

Conversation

mbhaskar
Copy link
Member

When a collection split occurs during bulk opertions, the requests were still being retried on the original partition as the partitionkeyrange cache that helps in routing was not being refreshed correctly. The effect is that the user received a failure with a status code 410 and substatus code 1002.
This PR addresses the above issue by refreshing the partitionkeyrange cache when a collection split occurs

Fixes #21126

@mbhaskar
Copy link
Member Author

/azp run java - cosmos - tests

@azure-pipelines
Copy link

Azure Pipelines successfully started running 1 pipeline(s).

…ValidationTests::splitQueryContinuationToken
@mbhaskar
Copy link
Member Author

/azp run java - cosmos - tests

@azure-pipelines
Copy link

Azure Pipelines successfully started running 1 pipeline(s).

@mbhaskar
Copy link
Member Author

/azp run java - cosmos - tests

@azure-pipelines
Copy link

Azure Pipelines successfully started running 1 pipeline(s).

Copy link
Member

@FabianMeiswinkel FabianMeiswinkel left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks - LGTM. I will block Spark Connector GA on this PR being merged

@moderakh moderakh self-requested a review May 14, 2021 16:53
Copy link
Contributor

@moderakh moderakh left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

how do we differentiate between GW vs Direct mode?

isn't only GW mode affected by the bug?

Implementing PR comments
Increasing timeout on tests
@mbhaskar
Copy link
Member Author

how do we differentiate between GW vs Direct mode?

isn't only GW mode affected by the bug?

Only GW mode is effected by this bug. GoneAndRetryWithRetryPolicy should take care of this in direct mode

@mbhaskar
Copy link
Member Author

/azp run java - cosmos - tests

@azure-pipelines
Copy link

Azure Pipelines successfully started running 1 pipeline(s).

@mbhaskar mbhaskar enabled auto-merge (squash) May 17, 2021 08:16
@FabianMeiswinkel
Copy link
Member

/check-enforcer evaluate

@mbhaskar mbhaskar merged commit 1ab1784 into Azure:master May 17, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

[BUG] Azure Cosmos DB 4.13 - Bulk on Gateway mode
4 participants