Back off transient LMDB read retries#2858
Merged
Merged
Conversation
Concurrent .tydb readers can hit raw OS-level LMDB errors while opening a read transaction or its database handle against a freshly opened environment. The retry path already keeps semantic LMDB errors visible, but its retry window was too short for temporary lock-table races. Keep the same transient-error classification and use a larger retry window, so opening a read transaction has more time to settle before reporting a real LMDB failure.
plajjan
force-pushed
the
lmdb-transient-backoff
branch
from
June 3, 2026 21:55
d2fefb5 to
dfd2d97
Compare
plajjan
changed the title
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Concurrent
.tydbreaders can still receive raw OS-level LMDB errors while opening a read transaction or its database handle against a freshly opened environment. The existing retry path keeps semantic LMDB failures visible, but its retry window was too short for temporary lock-table races.This keeps the same transient-error classification and gives those read transaction retries a larger window, so a temporary lock-table race can settle before we report a real LMDB failure.