[Feature Request] - Jobs.stop - stop all instances...

[gary-menzel]

Given Dominator is a central point, it may be possible to implement a flag in the Dominator record that, if set, means the instance will stop itself. With that, it would be possible to pass a "stop all" flag to Jobs.stop in a multi-instance environment (to be able to stop queues across ALL servers by setting the flag in the dominator record).

Similarly, all instances could be restarted again by changing the flag back.

It's an "emergency" thing - in case jobs are going crazy.

[msavin]

Indeed - it is under consideration.

[wildhart]

If you really need this in a hurry then you could try my 'fork' which as of today allows Jobs.stop and Jobs.start to work in a multi-server environment, using a flag in the dominator record as you suggest.

It's mostly API compatible with SteveJobs so could be a drop-in replacement if you don't need job history or job data. You should also be able to switch back easily when this feature is available in SteveJobs - my fork is more of a proof-of-concept than something I intend to maintain, although it's working happily for me in production. I strongly advise you to test it locally and on staging server(s) first.

Do your jobs actually go crazy (if so, do you know why?), or is this just-in-case?