Provide option which keeps jobs running on current worker

[Elliot Hesp]

Use case:

If debugging on a cluster setup with multiple users using it, then jobs will be shared across them. Having a sticky option on a job which always runs the subsequent jobs on the server it was created from would be really handy.

[Mike Diarmid]

I think there needs to be some logic around monitoring what workers are there, keeping a track of the id, the host name, pid, running jobs, active queues etc. Then something like this would be much easier to implement.

I think the implementation of this would mean having an internal queue per worker that all sticky jobs go through - would have to bypass non worker queues. Unless anyone can think of a better way?