Use cases:
$ ./bin/worker kill --class X # Kill all queued tasks of class X $ ./bin/worker kill --unknown # Kill all queued tasks with unknown classes. $ ./bin/worker kill --failures 8 # Kill all queued tasks with 8 or more failures.
Description
Description
Revisions and Commits
Revisions and Commits
| rP Phabricator | |||
| D16267 | rPc510c925cf87 Allow worker tasks to be cancelled by classname | ||
| D11736 | rP6f90fbdef806 Send emails for email invites | ||
| D10939 | rP9a7383121dbb Move cancel/retry/free task queue actions to bin/worker | ||
| D10894 | rP7e1c31218395 Add `bin/worker flood`, for flooding the task queue with work | ||
| Status | Assigned | Task | ||
|---|---|---|---|---|
| Resolved | epriestley | T3554 Implement a `bin/worker kill <criteria>` for batch-flushing tasks from the queue | ||
| Restricted Maniphest Task | ||||
| Restricted Maniphest Task | ||||
| Duplicate | epriestley | T7079 Implement `bin/worker purge` or similar to destroy tasks with unknown task classes |
Event Timeline
Comment Actions
We have flood, free, cancel and retry workflows now; the exec (run a task by ID in the foreground) and kill (bulk-cancel tasks by query-like selection) workflows described in the original description would probably be the most useful additions at this point. kill might not be a very good name, the desired behavior is more like cancel-all-tasks-matching [conditions].