[MRESOLVER-521] Improve congested file locks behaviour #455
Conversation
This file contains 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
Instead to immediately give up and sleep, they will sit a while to enter critical region. This is important for "hot" locks.
cstamas
changed the title
gnodet
approved these changes
Apr 3, 2024
cstamas
added a commit
to cstamas/maven-resolver
that referenced
this pull request
Apr 10, 2024
Instead to immediately give up and sleep, they will sit a while to enter critical region. This is important for "hot" locks. Explanation: currently a "loser" will _immediately give up_ and will go to sleep 100ms if cannot enter critical region, even if winner exits critical region within next 5ms. The retry is needed to ensure that it is retried as much as given time/unit takes, that was before consumed by constant retries+sleeps. The logic still works, as if tryLock spends time/unit waiting on criticalRegion (which is possible only on VERY HIGHLY congested locks), there will be no retry happening. --- https://issues.apache.org/jira/browse/MRESOLVER-522
cstamas
added a commit
that referenced
this pull request
Apr 10, 2024
Instead to immediately give up and sleep, they will sit a while to enter critical region. This is important for "hot" locks. Explanation: currently a "loser" will _immediately give up_ and will go to sleep 100ms if cannot enter critical region, even if winner exits critical region within next 5ms. The retry is needed to ensure that it is retried as much as given time/unit takes, that was before consumed by constant retries+sleeps. The logic still works, as if tryLock spends time/unit waiting on criticalRegion (which is possible only on VERY HIGHLY congested locks), there will be no retry happening. Backport of 089796b --- https://issues.apache.org/jira/browse/MRESOLVER-522
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Instead to immediately give up and sleep, they will sit a while to enter critical region. This is important for "hot" locks.
Explanation: currently a "loser" will immediately give up and will go to sleep 100ms if cannot enter critical region, even if winner exits critical region within next 5ms. The retry is needed to ensure that it is retried as much as given time/unit takes, that was before consumed by constant retries+sleeps. The logic still works, as if tryLock spends time/unit waiting on criticalRegion (which is possible only on VERY HIGHLY congested locks), there will be no retry happening.
https://issues.apache.org/jira/browse/MRESOLVER-521