Closed Bug 1445068 Opened 6 years ago Closed 6 years ago

processor on -new-stage not processing

Categories

(Socorro :: Infra, task, P1)

Product:
Socorro
Component:
Infra
Type:
task

Tracking

(Not tracked)

Status:
RESOLVED INVALID

People

(Reporter: willkg, Assigned: willkg)

References

Details

I'm comparing -stage with -new-stage and it looks like -new-stage isn't processing crashes. The most recent crash on -new-stage is  2018-03-10 12:11:46 which is a couple of days ago.

This bug covers figuring out why and rectifying the issue.
Making this a P1. It's after the end of my work day right now, but I can look into this tomorrow if no one beats me to it. My first step would be to check sentry for -new-stage, then check the processor logs.
Priority: -- → P1
Miles pointed out -new-stage has a queue of 600,000 things and so it's backlogged from the S3DistCpSOULCRUSHINGTODOLIST.

I'll grab this and revisit it in two days. It's entirely possible everything is fine.
Assignee: nobody → willkg
Status: NEW → ASSIGNED
-new-stage is all caught up with its queue.

I re-tested and everything is fine. Closing this out as INVALID.
Status: ASSIGNED → RESOLVED
Closed: 6 years ago
Resolution: --- → INVALID
You need to log in before you can comment on or make changes to this bug.