Closed Bug 1183608 Opened 11 years ago Closed 11 years ago

RabbitMQ acks not necessarily happening

Categories

(Socorro :: Backend, task)

Product:
Socorro
Component:
Backend
Type:
task
Priority:
Not set
Severity:
normal

Tracking

(Not tracked)

Status:
RESOLVED FIXED

People

(Reporter: lars, Unassigned)

Details

RabbitMQ is reporting that there are growing numbers of unacknowledged jobs. These jobs will sit in the queue forever until the worker's connection to RMQ is closed. Experiments in instrumentation have shown no acknowledged crashes. to do: instrument more fully so all the processors can be audited for unacknowledged crashes. Prepare the processor queuing system to periodically close and reopen the connection to RabbitMQ to ensure that unacknowledged crashes actually get re-offered to other processors.
Commit pushed to master at https://github.com/mozilla/socorro https://github.com/mozilla/socorro/commit/166cb93cdff13e02cd51bf4cee7f6efa25e41093 Merge pull request #2898 from twobraids/lonely-rabbits Fixes Bug1183608 - added logging to assist in confirming acks
Status: NEW → RESOLVED
Closed: 11 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.