Closed
Bug 1453310
Opened 7 years ago
Closed 5 years ago
Handle MAX_MODIFY_ATTEMPTS exhausted in claimWork
Categories
(Taskcluster :: Services, enhancement, P5)
Taskcluster
Services
Tracking
(Not tracked)
RESOLVED
WONTFIX
People
(Reporter: dustin, Unassigned)
References
Details
Attachments
(1 file)
|
(deleted),
text/x-github-pull-request
|
Details |
We have some Sentry errors to this effect.
It's probably OK that we exceed this limit for heavily used workerTypes. However, in that case we should catch the exception and handle it gracefully, rather than sending it to Sentry.
|
||
Comment 1•6 years ago
|
||
|
|
||
Comment 2•6 years ago
|
||
If it's OK to exceed the limit, let's focus on moving the queue to postgres.
|
Assignee | |
Updated•6 years ago
|
Component: Queue → Services
|
Reporter | |
Updated•5 years ago
|
Status: NEW → RESOLVED
Closed: 5 years ago
Resolution: --- → WONTFIX
You need to log in
before you can comment on or make changes to this bug.
Description
•