Page MenuHomePhabricator

Queue retry logic shouldn't use original enqueued date
Open, Needs TriagePublic2 Estimated Story Points

Description

Contributing factor in T192591 - We had the jobs shut down for more hours than requeue-max-age, so when we threw the first RetryableException, the message was already deemed to be too old to retry. We used the original enqueued date as a way to not clutter the message too much, since we're mixing body fields with what used to be headers. We should just reintroduce a field for retry count.

Event Timeline

Change 428032 had a related patch set uploaded (by Ejegg; owner: Ejegg):
[wikimedia/fundraising/SmashPig@master] Use a new field to track retry count instead of age

https://gerrit.wikimedia.org/r/428032

DStrine set the point value for this task to 2.Apr 23 2018, 7:43 PM
DStrine moved this task from Triage to Sprint +1 on the Fundraising-Backlog board.

Change 428032 abandoned by Ejegg:

[wikimedia/fundraising/SmashPig@master] Use a new field to track retry count instead of age

Reason:

https://gerrit.wikimedia.org/r/428032