The history for a job that had an action added is all screwed up.
rhettg@batch2:/nail/live/yelp$ tronview business_ad_report_daily.17
Job Run: business_ad_report_daily.17
State: UNKWN
Node: batch6
Action ID State Start Time End Time Duration
.run SUCC 2010-09-27 01:00:00 2010-09-27 05:11:59 4:11:59
.generate_ad_even... QUE - - -
These jobs all ran fine, but now that there is a new action it get's confused. I remember talking about this potential issue before, something that might be resolved by storing some sort of config history.
The history for a job that had an action added is all screwed up.
These jobs all ran fine, but now that there is a new action it get's confused. I remember talking about this potential issue before, something that might be resolved by storing some sort of config history.