-
-
Notifications
You must be signed in to change notification settings - Fork 4.2k
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
Add retry logic to cover deadlock situations during move operations #44504
Add retry logic to cover deadlock situations during move operations #44504
Conversation
a70f870
to
02476db
Compare
aa36481
to
81cc3a5
Compare
6b3665c
to
f9cc3f7
Compare
6b63644
to
f16632a
Compare
f16632a
to
d945191
Compare
7d33b1c
to
eded22f
Compare
/backport to stable28 |
/backport to stable27 |
/backport to stable26 |
eded22f
to
3238a3a
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think I like it, especially if it works? Did not test yet.
Is there anyway to let the DB or our Query layer handle that? Have some kind of generic way of saying «run this query in a transaction, if it deadlocks retry up to X times» ?
3238a3a
to
d297f81
Compare
…g many files Signed-off-by: Louis Chemineau <louis@chmn.me>
d297f81
to
7517959
Compare
/backport to stable27 |
/backport to stable28 |
related to #44504 Signed-off-by: Matthieu Gallien <matthieu.gallien@nextcloud.com>
Should help with #43759