[Taskforest-discuss] Suppressing passed runs for jobs using "every" when TaskForest has been down
Brought to you by:
enoor
From: Fredrik E. <fe...@ds...> - 2011-05-12 14:45:43
|
Dear TaskForest users and developers, I've been evaluating TaskForest as a solution for one of our clients and the down to basics approach really appeals to me. However, I have a question that I haven't been able to answer during my evaluation. This case concerns a very frequent job with a family that looks like this: ---FAM1 | start => '00:01', tz => 'Europe/Stockholm', days => 'Mon,Tue,Wed,Thu,Fri,Sat,Sun' | | myfrequentjob(every => '5', until => '23:59') --- I want the job to run every five minutes, always. This one is a bit extreme but we have a few of these jobs but which will have a lesser frequency and a different until time. My problem is that if, for some reason (maybe the machine was down), TaskForest has not been running for half a day and is then started, I would like recurring jobs like this to pick up where we are now and just start running every five minutes. This is not the way TaskForest handles it, I find that my "myfrequentjob" might run a hundred times (depending on when I start TaskForest of course), to catch up for missed runs, until it settles into the five minute frequency. My questions to you are: 1) Have I missed something, is it possible to suppress job with a passed run time, for a recurring job (one that uses "every")? 2) Is there another way of handling this situation within TaskForest? Of course I could use cron, but that would mean I had to monitor these jobs separately and I wouldn't see the full picture in TaskForest. Thanks for your time. Regards Fredrik Engberg |