We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
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.
The text was updated successfully, but these errors were encountered:
Closing per #23145
Sorry, something went wrong.
No branches or pull requests
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.
The text was updated successfully, but these errors were encountered: