Version 689.v731678c3e0eb_
Jenkins Version: 2.426.1
We are coming across an issue where when we create a role, it causes Jenkins to timeout, and many times causes it to become unstable and inaccessible. This happens in the UI and API.
Running a simple `curl localhost:8080/role-strategy/strategy/addRole` will cause the curl command to hang until our load balancer this sits behind produces a timeout (which is of 180 seconds). Running this or even going through the UI also causes Jenkins to become inaccessible until we forcibly restart it.
Our Jenkins instance is utilized heavily, with over 250 roles and project folders. I would understand if the large amount of roles/projects causes issues to load in the UI, but why would it behave the same at the API level?
Read requests seem to work fine though. It seems only updating/creating roles where this happens.
Originally reported by ehuizar1028, imported from: Role Based Authorization Strategy causing timeouts
- assignee:
oleg_nenashev
- status: Open
- priority: Minor
- component(s): role-strategy-plugin
- resolution: Unresolved
- votes: 0
- watchers: 1
- imported: 20251211-223321
Raw content of original issue
Version 689.v731678c3e0eb_
Jenkins Version: 2.426.1
We are coming across an issue where when we create a role, it causes Jenkins to timeout, and many times causes it to become unstable and inaccessible. This happens in the UI and API.
Running a simple `curl localhost:8080/role-strategy/strategy/addRole` will cause the curl command to hang until our load balancer this sits behind produces a timeout (which is of 180 seconds). Running this or even going through the UI also causes Jenkins to become inaccessible until we forcibly restart it.
Our Jenkins instance is utilized heavily, with over 250 roles and project folders. I would understand if the large amount of roles/projects causes issues to load in the UI, but why would it behave the same at the API level?
Read requests seem to work fine though. It seems only updating/creating roles where this happens.
Version 689.v731678c3e0eb_
Jenkins Version: 2.426.1
We are coming across an issue where when we create a role, it causes Jenkins to timeout, and many times causes it to become unstable and inaccessible. This happens in the UI and API.
Running a simple `curl localhost:8080/role-strategy/strategy/addRole` will cause the curl command to hang until our load balancer this sits behind produces a timeout (which is of 180 seconds). Running this or even going through the UI also causes Jenkins to become inaccessible until we forcibly restart it.
Our Jenkins instance is utilized heavily, with over 250 roles and project folders. I would understand if the large amount of roles/projects causes issues to load in the UI, but why would it behave the same at the API level?
Read requests seem to work fine though. It seems only updating/creating roles where this happens.
Originally reported by ehuizar1028, imported from: Role Based Authorization Strategy causing timeouts
Raw content of original issue