fix(2079/deadlock): avoid deadlock by updating env individually #3339
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.
Thanks for submitting a PR! Please check the boxes below:
pre-commit
to check lintingdocs/
if required so people know about the feature!Changes
As documented here the cause of the deadlock was this where clause
.... where project_id=<>
. This PR avoids that by updating theupdated_at
for every environment individually, i.e:...where environment_id=<>
Note: the duplicate signals issue is not relevant any more because we exclude
updated_at
from historical trackingHow did you test this code?
I attempted to reproduce this on staging by updating segments for a project using
wrk
(10 threads, 10 connections), but I could not. However, based on reasoning, this should work.