You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
As a Herd LFS user I want to minimize the amount of time that LFS operations hold database transactions so I can reduce the possibility that a concurrent user operation will receive an optimistic locking error.
Acceptance Criteria
LFS file operation that occurs during clean-up does not hold a database transaction while performing the S3 delete operation
Any failure in the S3 delete operation fails does not impact the database transaction that updates BData Status.
Note that current logic does not even react to failure of S3 delete operation – the transaction to update BData Status is committed either way. So there is no logical change and no reason to have the transaction around the S3 operation anyway.
The text was updated successfully, but these errors were encountered:
As a Herd LFS user I want to minimize the amount of time that LFS operations hold database transactions so I can reduce the possibility that a concurrent user operation will receive an optimistic locking error.
Acceptance Criteria
The text was updated successfully, but these errors were encountered: