-
-
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
Revert "Revert "Remove inefficient fed share scanner"" #32852
Conversation
@icewind1991 what do you think of disabling the locking as the original federated shares also didn't have locking and this is causing some issues? |
Having an integration test for the failing case from #31554 would be good I think. There is one that looks like it could catch that but the file upload part is commented out f6a1286#diff-3d1fc871fd7bb42743321aa17f6abae00336d14755e5992ee3d5c34890c685eeR243-R245 |
This reverts commit 6667007. Signed-off-by: Carl Schwan <[email protected]>
The old inneficiant code didn't do locking and adding locking is creating issues Signed-off-by: Carl Schwan <[email protected]>
Signed-off-by: Robin Appelman <[email protected]>
4f52670
to
8367b99
Compare
The external scanner wasn't respecting the updater's request to disable locking (as the updater is triggered while we already have an exclusive lock) fix is added to the PR. With this I can upload to fed. shared without issue |
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.
👍 makes a lot of sense
/backport to stable24 |
/backport to stable23 |
This reverts commit 6667007.
See context in #32806, this is breaking things
Fixes #31554