change job queue status from cli

[kaplanelad]

#1039

[jondot]

Reading the conversation on #1039 I believe this has to add some kind of "selector". This is my logic:

1. This kind of change status is probably relevant mostly or only in processing->queue which means it can be called requeue
2. For the specific use case describe, the most ideal solution would be to encode some kind of versioning scheme. Why was a worker cut off? a redeploy? then, encode a software version. This means we can requeue all "old version" jobs. The selector is a version. The version can be software version, deploy version, etc. --- anything that can separate between "old workers which were cut off" and "new workers that are online now", because new workers will set other jobs to "processing" in real-time, which are unrelated to the jobs we're trying to requeue.
3. Since (2) may be complicated, the best solution may be to requeue based on a time cut off (requeue anything that was updated to processed 1 hour before now, or X time before now)

[kaplanelad]

Reading the conversation on #1039 I believe this has to add some kind of "selector". This is my logic:

1. This kind of change status is probably relevant mostly or only in processing->queue which means it can be called requeue
2. For the specific use case describe, the most ideal solution would be to encode some kind of versioning scheme. Why was a worker cut off? a redeploy? then, encode a software version. This means we can requeue all "old version" jobs. The selector is a version. The version can be software version, deploy version, etc. --- anything that can separate between "old workers which were cut off" and "new workers that are online now", because new workers will set other jobs to "processing" in real-time, which are unrelated to the jobs we're trying to requeue.
3. Since (2) may be complicated, the best solution may be to requeue based on a time cut off (requeue anything that was updated to processed 1 hour before now, or X time before now)

changed