[JENKINS-50568] Receiving Workers thread are not reconfigurable without Jenkins restart

We today had the problem that the receiving workers queue was somehow stuck and we have piled up 800k events. After reconnecting the event listener events were processed again, but with only 8 threads and 18k jobs it would take over 10h to process all events (even though 99% of the events are replication events which are not of interest for us). Changing the # of receiving worker threads has no effect. Looking at the code this requires a restart of Jenkins.

JENKINS-20120 only solved the thing for the sending queue

---
Originally reported by mawinter69, imported from: Receiving Workers thread are not reconfigurable without Jenkins restart

• assignee: rsandell
  
• status: Open
  
• priority: Major
  
• component(s): gerrit-trigger-plugin
  
• resolution: Unresolved
  
• votes: 0
  
• watchers: 2
  
• imported: 2025-12-07
  

We today had the problem that the receiving workers queue was somehow stuck and we have piled up 800k events. After reconnecting the event listener events were processed again, but with only 8 threads and 18k jobs it would take over 10h to process all events (even though 99% of the events are replication events which are not of interest for us). Changing the # of receiving worker threads has no effect. Looking at the code this requires a restart of Jenkins.


JENKINS-20120 only solved the thing for the sending queue

• environment: gerrit-trigger-plugin 2.27.5

Start in the gerrit-trigger-plugin code that manages receiving worker threads and compare its configuration behavior with the referenced JENKINS-20120 change for the sending queue. Confirm the receiving worker count can be changed through configuration while Jenkins is running, and verify that the queue uses the updated count without a restart.

Written by the indexing model from the issue text.