Kill running jobs

[mojolicious]

Kill running jobs

[kraih]

A worker remote control command system has just been added. 4054eac

[kraih]

This sounds like a worker remote control feature for an Admin UI. We could allow active jobs to be killed, worker pools to grow/shrink, and maybe even change the queues a worker is watching. Doubt we'll see this before #25 has been implemented though.

[avkhozov]

May be worker remote control feature can be done not only for Admin UI, but also for minion admin sub-commands? Sometimes shell commands more convenient for automation than a web interface.

[kraih]

I've thought a little bit about this, and on the database layer this might be easiest to implement by adding an inbox column (array of jsonb perhaps) to the minion_workers table. New broadcast messages could be added to the inbox with a new backend method like send_worker($worker_id, {some => 'data'}), and we would remove all messages from the inbox with the already existing register_worker method at the same time heartbeats are handled.

How those messages are then processed inside the worker process shouldn't be too hard to figure out. And sending them from the job command would be trivial as well.

[kraih]

The broadcast mechanism could also be used for #34.

[kraih]

It would be pretty easy now to add a command to kill a specific job remotely, we just have to figure out portability issues. Perhaps we should just stop supporting versions of Perl with fork emulation, like we did in Mojolicious for subprocesses.

[kraih]

And you can now kill jobs remotely too. 1360f5a

[avkhozov]

Thanks!