This is how most of our CRM jobs manage their duty cycle, it's superior to processing a fixed record count because it's independent of system load and changes in complexity, and ensures the thing we care about most: never overlap jobs.
Description
Description
| Status | Subtype | Assigned | Task | ||
|---|---|---|---|---|---|
| Restricted Task | |||||
| Resolved | awight | T92922 Use the new queue wrapper for limbo, antimessage, and orphan slaying | |||
| Resolved | awight | T99018 Stop writing to ActiveMQ once orphan slaying on Redis has been tested | |||
| Restricted Task | |||||
| Resolved | awight | T99017 Orphan slayer reads from frack Redis rather than ActiveMQ | |||
| Invalid | awight | T107958 Reduce cheesiness: Abort orphan slayer job when we hit a total elapsed time like 4 minutes |