See this Comm Center thread by Petri Kehusmaa. If the scheduler is not running, fixed time plans that have been started are left "running" and thus cannot be edited.

 

  
SVN Comment
 
 

  
Author
  
rbdenny
 
 

  
Repository
  
svn+ssh://rbdenny@a2_svn_dc3/home/rbdenny/svn/astro/scheduler
 
 

  
SVN Revision
  
698
 
 

  
Affected files
  
/trunk/Help/RelNotes.htm (Modified)
/trunk/Scheduler/Engine.cs (Modified)
/trunk/Scheduler/MainForm.cs (Modified)

 
 

  
Check-in comment
  
Prevent fixed time plans from being left running if the dispatcher is stopped or if the scheduler is shut down with the dispatcher running.
GEM:1308

 

What if the scheduler is truly "killed" as in Task Scheduler or the Stop box with the dispatcher running (ugly kill)? Probably need to have a process that looks for running plans at startup and just resubmits them. Already done on Scheduler startup:



DB.MarkUncompletedPlansPending

The handling of Fixed Time plans when failed by constraints at specified start time needs some improvement as well. (done in SCHEDULER-1624)

Since the Plan "must run" at a given time, what should we do with it? The Plan is marked "running" as soon as the scheduler starts if it is for tonight, thus reserving the time slot(s). If the Scheduler is killed before its (first) time slot, just requeue it and let it get started again. If the scheduler is killed after the stat of the (first) time slot, it is a failure no matter what. Fail it.



This took some thought.