If a node is scheduled by hour, the node is scheduled to run once every N hours within a specific period every day. For example, a node is scheduled to run once every hour from 00:00 to 03:00 every day.

Precautions

  • The period within which a node is scheduled to run is a left-closed, right-closed interval. For example, if a node is scheduled to run once every hour from 00:00 to 03:00, the scheduling system generates four instances for the node every day, and the instances are scheduled to run in sequence at 00:00, 01:00, 02:00, and 03:00.
  • You can schedule a node to run at specified intervals within a specific period every day. You can also schedule the node to run at specified points in time on the hour every day.
  • The actual time at which a node is run may be different from the scheduling time of the node due to reasons such as insufficient resources.

Configuration example

  • Configuration method

    On the DataStudio page, create a node and go to the configuration tab of the node. Click the Properties tab in the right-side navigation pane. In the General section of the Properties tab, configure the scheduling period for the node.

  • Scenario
    • Configuration details
      The following figure shows how to configure a node to be scheduled to run at an interval of 6 hours from 00:00 to 23:59 every day.
      Note The cron expression is automatically generated based on the scheduling time that you select and cannot be changed.
      Schedule a node by hour
    • Scheduling details
      The scheduling system generates four instances for the node every day and schedules the instances to run in sequence at 00:00, 06:00, 12:00, and 18:00. Node scheduled by hour

Scenario: A node scheduled by hour depends on a node that has the same or a different scheduling frequency

DataWorks allows you to configure scheduling dependencies between the nodes whose scheduling frequencies are different. Before you configure scheduling dependencies, you can learn the principles of configuring scheduling dependencies. After you have a command of the principles, you can configure the scheduling dependencies of nodes based on your business requirements. For information about scheduling dependencies in complex dependency scenarios and the related illustrations, see Principles and samples of scheduling configurations in complex dependency scenarios.

The following information describes the scheduling dependencies of the instances generated for a node scheduled by hour if the node depends on a node that has the same or a different scheduling frequency. You can refer to illustrations in Principles and samples of scheduling configurations in complex dependency scenarios to understand the information.
  • The node depends on another node scheduled by hour:
    • If the numbers of scheduling cycles of the two nodes on the current day are different, the instances generated for the descendant node on the current day depend on the instances generated for the ancestor node on the current day based on the scheduling time of the descendant node in each scheduling cycle.
    • If the numbers of scheduling cycles of the two nodes on the current day are the same, the instance generated for the descendant node in a scheduling cycle depends on the instance generated for the ancestor node in the same scheduling cycle. The scheduling dependencies of the instances generated for the descendant node on the instances generated for the ancestor node are unrelated to the scheduling time in each scheduling cycle, but are related to the sequence number of a scheduling cycle.
  • The node depends on a node scheduled by day: The instances generated for the descendant node on the current day depend on the instance generated for the ancestor node on the current day. The instances generated for the descendant node can start to run only after the instance generated for the ancestor node is successfully run.
  • The node depends on a node scheduled by minute: The instance generated for the descendant node in a scheduling cycle depends on all instances generated for the ancestor node during the period represented by the scheduling cycle.