Skip to content
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

Harden AWS transaction locking mechanism to support long running I/O operations #12008

Closed
Tracked by #11296
homar opened this issue Apr 19, 2022 · 1 comment
Closed
Tracked by #11296

Comments

@homar
Copy link
Member

homar commented Apr 19, 2022

Currently, AWS transaction log locking assumes that operation under lock will return within 5 minutes.

After 5 minutes lock is assumed expired and if file was written after that grace period we may have conflicting writes from two transactions.

The mechanism can be improved by refreshing the lock in separate thread, while operation under log is in progress.

@wendigo
Copy link
Contributor

wendigo commented Sep 4, 2024

Closing per #23145

@wendigo wendigo closed this as completed Sep 4, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

No branches or pull requests

2 participants