jenkinsci / jenkinsci/gerrit-trigger-plugin

[JENKINS-33959] What causes "Gerrit-trigger send commands queue contains <N> items!"

Open
#776 3 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

component:gerrit-trigger-plugin imported-jira-issue priority:minor resolution:unresolved
Dominant language
Java
Stars
226
Forks
289
PR merge metrics
No merged PRs in 30d

Description

Not really a great bug report but... Jenkins stopped casting its +1/-1 Verified votes on Gerrit, despite the builds working fine, and I see no errors either in Gerrit's log or Jenkins' log, but the jenkins/manage page says

The Gerrit-trigger send commands queue contains 127 items!
Something might be stuck, or your system can't process the commands fast enough. Try to increase the number of sending worker threads on the Gerrit configuration page.

How can we troubleshoot what's wrong, knowing that nothing has changed recently and things have been up and working for a while?


Originally reported by tsuna, imported from: What causes "Gerrit-trigger send commands queue contains items!"
  • assignee: rsandell
  • status: Open
  • priority: Minor
  • component(s): gerrit-trigger-plugin
  • resolution: Unresolved
  • votes: 0
  • watchers: 5
  • imported: 2025-12-06
Raw content of original issue

Not really a great bug report but... Jenkins stopped casting its +1/-1 Verified votes on Gerrit, despite the builds working fine, and I see no errors either in Gerrit's log or Jenkins' log, but the jenkins/manage page says

The Gerrit-trigger send commands queue contains 127 items! Something might be stuck, or your system can't process the commands fast enough. Try to increase the number of sending worker threads on the Gerrit configuration page.

How can we troubleshoot what's wrong, knowing that nothing has changed recently and things have been up and working for a while?

  • environment: Linux with 1.8.0_65, Jenkins 1.652, , Gerrit 2.12.2, Gerrit Trigger Plugin 2.18.4

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start at the jenkins/manage page warning and the Gerrit configuration page's sending-worker settings, then trace how the send commands queue is processed. Reproduce or inspect the stalled queue and available Jenkins and Gerrit logs; done means identifying the cause of the backlog and defining a verified corrective change.

Written by the indexing model from the issue text.

Assessment

Tech stack
java
Domain
devops
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
20/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.