Use select_for_update() to lock row of table to fix race condition on update user's quota.
Fix issue where size of previously deleted files would duplicately reduced from user's quota when deleting directory.
Changes
Use select_for_update() to lock row of table to fix race condition on update user's quota.
Fix issue where size of previously deleted files would duplicately reduced from user's quota when deleting directory.
QA Notes
Does this change require a data migration? If so, what data will we migrate?
What is the level of risk?
Any permissions code touched?
Is this an additive or subtractive change, other?
How can QA verify? (Through UI, API, AdminApp or AdminAdminApp?)
If verifying through API, what's the new version? Please include the endpoints in PR notes or Dev docs.
What features or workflows might this change impact?
Purpose
Use select_for_update() to lock row of table to fix race condition on update user's quota. Fix issue where size of previously deleted files would duplicately reduced from user's quota when deleting directory.
Changes
Use select_for_update() to lock row of table to fix race condition on update user's quota. Fix issue where size of previously deleted files would duplicately reduced from user's quota when deleting directory.
QA Notes
Documentation
Side Effects
Ticket
GRDM-39988