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

Prevent element creation in case of concurrent deletions #1117

Closed
richard-julien opened this issue Feb 27, 2021 · 0 comments
Closed

Prevent element creation in case of concurrent deletions #1117

richard-julien opened this issue Feb 27, 2021 · 0 comments
Assignees
Labels
feature use for describing a new feature to develop solved use to identify issue that has been solved (must be linked to the solving PR)
Milestone

Comments

@richard-julien
Copy link
Member

Problem to Solve

In some high concurrent case the platform can create partial information when a concurrent deletion occurs.
This situation can lead to incorrect data stored in the database

Current Workaround

No

Proposed Solution

  1. Deletion must lock the element.
  2. We also need to put deleted elements in a temporary cache to check this deletion concurrency after locking the elements.
@richard-julien richard-julien added this to the Release 4.3.0 milestone Feb 27, 2021
@richard-julien richard-julien self-assigned this Feb 27, 2021
@richard-julien richard-julien added the feature use for describing a new feature to develop label Feb 27, 2021
@richard-julien richard-julien added the solved use to identify issue that has been solved (must be linked to the solving PR) label Feb 27, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
feature use for describing a new feature to develop solved use to identify issue that has been solved (must be linked to the solving PR)
Projects
None yet
Development

No branches or pull requests

1 participant