Skip to content

Avoid deadlock merge requests order - #4

Open
FreCap wants to merge 10 commits into
master-accepting-MRfrom
avoid-deadlock-merge-requests-order
Open

Avoid deadlock merge requests order#4
FreCap wants to merge 10 commits into
master-accepting-MRfrom
avoid-deadlock-merge-requests-order

Conversation

@FreCap

@FreCap FreCap commented Sep 15, 2022

Copy link
Copy Markdown
Owner

No description provided.

fcapponi added 7 commits September 14, 2022 19:33
The existing code implies that the executor will always run the queries in order, but this is not a hard guarantee of the executor. This can cause newer merge batches getting in front of merge batches, and locking the thread, which causes a deadlock
The existing code implies that the executor will always run the queries in order, but this is not a hard guarantee of the executor. This can cause newer merge batches getting in front of merge batches, and locking the thread, which causes a deadlock
The existing code implies that the executor will always run the queries in order, but this is not a hard guarantee of the executor. This can cause newer merge batches getting in front of merge batches, and locking the thread, which causes a deadlock
FreCap added a commit that referenced this pull request Sep 15, 2022
@FreCap
FreCap force-pushed the master-accepting-MR branch from 015cf86 to 6d320cf Compare September 15, 2022 14:57
@FreCap
FreCap force-pushed the avoid-deadlock-merge-requests-order branch from ec48eb7 to fb7a5c7 Compare September 15, 2022 15:10
fcapponi added 3 commits September 15, 2022 13:24
* Avoid deadlock for wrong ordering execution of merge queries.
The existing code implies that the executor will always run the queries in order, but this is not a hard guarantee of the executor. This can cause newer merge batches getting in front of merge batches, and locking the thread, which causes a deadlock

Co-authored-by: fcapponi <francesco.capponi@worldquant.com>
* Avoid deadlock for wrong ordering execution of merge queries.
The existing code implies that the executor will always run the queries in order, but this is not a hard guarantee of the executor. This can cause newer merge batches getting in front of merge batches, and locking the thread, which causes a deadlock

Co-authored-by: fcapponi <francesco.capponi@worldquant.com>
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.

1 participant