634619 - Socorro - strange stuck job in processor

Status: RESOLVED WONTFIX

(Socorro :: General, task)

Description

[K Lars Lohn [:lars] [:klohn]]

on 2011-02-16, processor08 was excessively about skipping a job that was already seen.  Investigate and resolve this problem.

thousands of these are in the log:

2011-02-16 09:02:05,734 DEBUG - MainThread - Skipping already seen job (227178734, 'd00eacc9-d4bc-42ae-9825-f0e052110215', 1)
2011-02-16 09:02:05,739 DEBUG - MainThread - Skipping already seen job (227178734, 'd00eacc9-d4bc-42ae-9825-f0e052110215', 1)
2011-02-16 09:02:05,743 DEBUG - MainThread - Skipping already seen job (227178734, 'd00eacc9-d4bc-42ae-9825-f0e052110215', 1)

Comment 1

[K Lars Lohn [:lars] [:klohn]]

If I recall correctly this was an issue with polling in the monitor application.  'standardLoopDelay' had been set to 0, which caused monitor to pester the PG queue.  Raising the value to 5 seconds resolved the problem.  This bug should have been closed long ago.

If you are experiencing this problem and are not in a position to upgrade to the latest version of Socorro that uses RabbitMQ rather than the 'monitor' app, then I suggest experimenting with various values for the 'standardLoopDelay' and/or the 'priorityLoopDelay' configuration values.

Comment 2

[Rigin Oommen]

what about the memory allocation

Comment 3

[K Lars Lohn [:lars] [:klohn]]

in the year since this bug was noted, the processor has evolved to new code. we're not seeing the problem anymore.