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.
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
Revert primary permits changes and add hook #120398
Revert primary permits changes and add hook #120398
Changes from all commits
275f5c0
95dba12
File filter
Filter by extension
Conversations
Jump to
There are no files selected for viewing
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
do we need to do the context preserving in all cases? I don't think so? i.e. during normal operations
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@fcofdez I'm not familiar with what operations need the context. I saw it in IndexShardOperationPermits.java and assumed it's needed here as well.
Note that before this PR, the IndexShardOperationPermits.java was the one potentially triggering the final listener of the operation. However, with this PR, we potentially add another blocking step in the plugin (the additional RefCountingListener here). So we can't be sure whatever thread finally triggers the RefCountingListener has the context, thus I elected to made sure we preserve the context as well to "replicate" the original behavior of IndexShardOperationPermits.java.
After this explanation, do you believe we can safely skip the context?