-
Notifications
You must be signed in to change notification settings - Fork 1.4k
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
Reduce locks during decision logging #6797
Merged
johanfylling
merged 4 commits into
open-policy-agent:main
from
mjungsbluth:remove_locks_decision_logs
Jun 12, 2024
Merged
Changes from 1 commit
Commits
Show all changes
4 commits
Select commit
Hold shift + click to select a range
3d6d2be
Reduce locks during decision logging
mjungsbluth 937b560
Re-emitting error caused by first (only) `PrepareForEval` on subseque…
johanfylling 273f481
Renaming `prepareOnce.prepare()` -> `prepareOnce.prepareOnce()`
johanfylling e716234
Merge branch 'main' into remove_locks_decision_logs
johanfylling File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
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.
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.
A benefit of the old mutex-based approach was that on error, the
PrepareForEval()
call would be retried on subsequent mask/drop calls. Now, if the first (and only) call toPrepareForEval()
fails for the current configuration, we'll end up with a brokenPreparedEvalQuery
that'll cause a panic when used.I've made a commit to your branch with a proposed fix and tests asserting the behavior. The fix simply re-emits the error for subsequent calls. I think it's unlikely that subsequent
PrepareForEval()
calls would have a different outcome, so we don't need to retain the old behavior where we retry.Thoughts?
This change shouldn't have an impact on performance, but if you're running separate tests on your end, please let us know how this fares.