Skip to content

Return CONFLICT for inserting items with duplicate client tags#62

Merged
yrliou merged 2 commits into
masterfrom
duplicate_client_tag_conflict
Feb 24, 2021
Merged

Return CONFLICT for inserting items with duplicate client tags#62
yrliou merged 2 commits into
masterfrom
duplicate_client_tag_conflict

Conversation

@yrliou
Copy link
Copy Markdown
Member

@yrliou yrliou commented Feb 24, 2021

We have seen cases that some clients kept getting TRANSIENT_ERROR when they trying to insert new items with duplicate client tags and cannot recover from it, and clients kept trying the same commits which cannot be accepted by the server due to duplicate client tags.
We are having a hard time to reproduce it, in theory we think return CONFLICT in this case makes more sense, the change is in the first commit of this PR.
The second commit is to limit the scope to specific clients first, and will be reverted pretty soon.

@yrliou yrliou self-assigned this Feb 24, 2021
@yrliou yrliou force-pushed the duplicate_client_tag_conflict branch 2 times, most recently from fba880b to 00d3195 Compare February 24, 2021 15:51
AlexeyBarabash
AlexeyBarabash previously approved these changes Feb 24, 2021
Copy link
Copy Markdown
Collaborator

@AlexeyBarabash AlexeyBarabash left a comment

Choose a reason for hiding this comment

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

++

This is a temporary approach, will be reverted really soon.
Copy link
Copy Markdown
Collaborator

@hspencer77 hspencer77 left a comment

Choose a reason for hiding this comment

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

Looks good.

@yrliou yrliou merged commit 3d3ddb9 into master Feb 24, 2021
@yrliou yrliou mentioned this pull request Feb 24, 2021
@mihaiplesa mihaiplesa deleted the duplicate_client_tag_conflict branch March 31, 2024 12:57
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants