Channel and Service Scheduling overview

Channels

Channel states are controlled by EC and the channel schedules can survive a EC restart. For example, when you restart EC, channels that are scheduled to pause remain on pause. To supersede the scheduled channel pause, manually invoke a pause or resume.

Example scenarios

Scenario Setting/Behavior
Offline schedule is every Saturday 1PM and runs for 1 minute (this is set in PA)

  • Default DiskIn is set to Pause/Resume.

  • Service ABC is set to Stop/Start.

Case 1 (Normal scenario):

EC is running

  • Default DiskIn will Pause at 1PM and Resume at 1:01PM.

  • Service ABC will Stop at 1PM and Resume at 1:01PM.

Case 2:

EC is shutdown at 12noon and started at 2PM manually

  • Default DiskIn is started (default behavior).

  • EC will start service ABC because according to schedule service ABC should be started.

Case 3:

EC is shutdown 10 seconds after 1PM and is manually started at 2PM.

  • Default DiskIn is Paused just before the EC shutdown, according to schedule.

    On startup, Default DiskIn will be started (default behavior).

  • Service ABC will be stopped just before shutdown, according to schedule.

    On startup, EC will start service ABC.

Case 4:

EC is shutdown at 12noon and started 30 seconds after 1PM

  • On startup, Default DiskIn will not start. According to schedule, Default DiskIn is still offline.

    Default DiskIn will start at 1:01PM on schedule.

  • On startup, Service ABC will be stopped. According to schedule, Service ABC is still offline.

    Service ABC will start at 1:01PM on schedule.

Case 5:

Default Disk is (Manually) Paused and Service ABC is (Manually) stopped at 12noon
Note: EC does not keep track of manual pause/stop.

  • Default DiskIn is set to Resume at 1:01PM.

  • Service ABC is set to Start at 1:01PM.