Totally agree, Hank (the acts of God part really made me laugh). The problem is that few people know their way around the workflow/conductor part of the software, but it would certainly be a nice feature if someone with enough knowledge can take the task.
Just to share my opinion, I think that a mechanism to force-delete a workflow instance, rather than a 'sel-destruct time' would be better. But I guess that's an open question. Best regards On 24 Feb, 2012 12:41, "Hank Magnuski" <[email protected]> wrote: > I'm not sure exactly how to articulate this request, and maybe one of > the system architects can formulate it more precisely, > but it seems there needs to be some kind of backup plan or timer or > fuse to blow up jobs that have failed processing (for > whatever happens to be the problem of the day) to clear the job queue > and get these things to a final state. > > I had a retract operation fail on me and now I'm looking at the > recordings listing and these jobs are listed as "Processing: Archived" > when clearly they are not processing, not going anywhere, and will > stay in that state forever until I do something (and I'm not sure what > that something is at the moment). > > Whoever spawned these things ought to look at them and see if they > complete in some reasonable time, and if they go belly up ought to > nuke them > and let the system get on with its life. > > $**+ happens for many unforseen reasons (bad code, bad data, acts of > God, etc.) and a robust system can deal with it at more than one > level. > > Hank > _______________________________________________ > Matterhorn-users mailing list > [email protected] > http://lists.opencastproject.org/mailman/listinfo/matterhorn-users >
_______________________________________________ Matterhorn-users mailing list [email protected] http://lists.opencastproject.org/mailman/listinfo/matterhorn-users
