-
Notifications
You must be signed in to change notification settings - Fork 24.9k
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
Move expensive role building off transport thread #113020
Move expensive role building off transport thread #113020
Conversation
...security/src/main/java/org/elasticsearch/xpack/security/authz/store/CompositeRolesStore.java
Show resolved
Hide resolved
...ity/src/test/java/org/elasticsearch/xpack/security/authz/store/CompositeRolesStoreTests.java
Show resolved
Hide resolved
Pinging @elastic/es-security (Team:Security) |
...security/src/main/java/org/elasticsearch/xpack/security/authz/store/CompositeRolesStore.java
Show resolved
Hide resolved
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.
LGTM 🚀
I've left only non-blocking comments add a suggestion to add more coverage around forking logic. Approving, since this should not require another round of review.
@elasticmachine update branch |
💚 Backport successful
|
This PR moves role building off the transport thread to the generic thread pool, since role building can be expensive depending on role structure. Role building is CPU bound so this PR uses a `ThrottledTaskRunner` to limit the number of concurrent requests. I will explore adding a max queue limit in a follow up. Resolves: ES-9505
💚 All backports created successfully
Questions ?Please refer to the Backport tool documentation |
This PR moves role building off the transport thread to the generic thread pool, since role building can be expensive depending on role structure. Role building is CPU bound so this PR uses a `ThrottledTaskRunner` to limit the number of concurrent requests. I will explore adding a max queue limit in a follow up. Resolves: ES-9505 (cherry picked from commit 6cdd59b)
This PR moves role building off the transport thread to the generic thread pool, since role building can be expensive depending on role structure. Role building is CPU bound so this PR uses a `ThrottledTaskRunner` to limit the number of concurrent requests. I will explore adding a max queue limit in a follow up. Resolves: ES-9505 Co-authored-by: Elastic Machine <[email protected]>
This PR moves role building off the transport thread to the generic thread pool, since role building can be expensive depending on role structure.
Role building is CPU bound so this PR uses a
ThrottledTaskRunner
to limit the number of concurrent requests. I will explore adding a max queue limit in a follow up.Resolves: ES-9505