If a node is scheduled by day, the node is automatically run once at a specified point in time every day. After you create an auto triggered node that is scheduled by day, the default scheduling time of the node is randomly generated from 00:00 to 00:30. You can change the scheduling time of the node based on your business requirements. For example, you can set the scheduling time of the node to 13:00.
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
- An import node, an analytics node, and an export node are scheduled by day.
- The scheduling time of the nodes is set to
13:00. - The analytics node depends on the import node, and the export node depends on the analytics node.
Note The cron expression is automatically generated based on the scheduling time that you select and cannot be changed.
- Scheduling detailsThe scheduling system automatically generates and runs instances for the nodes.
Note- The following prerequisites must be met before a node is run:
- The ancestor node of the node is successfully run.
- The scheduling time of the node arrives.
- The default scheduling time of a node that is scheduled by day is randomly generated from
00:00to00:30.
- The following prerequisites must be met before a node is run:
- Configuration details
Scenario: A node scheduled by day depends on a node scheduled by hour or minute
This section describes the scenarios in which a node scheduled by day needs to depend on a node scheduled by hour or minute and the impacts that are generated after the self-dependency is configured for the node scheduled by hour or minute.
Note 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 configurations in complex dependency scenarios, see Principles and samples of scheduling configurations in complex dependency scenarios.
Scheduling dependencies in scenarios in which a node scheduled by day depends on a node scheduled by hour or minute
| Scenario | Description |
|---|---|
| The instance generated for a node scheduled by day depends on all instances generated for a node scheduled by hour or minute by default. | By default, if you configure a node scheduled by hour or minute as the ancestor node of a node scheduled by day, the instance generated for the node scheduled by day on the current day depends on all instances generated for the node scheduled by hour or minute on the current day. After the output data of all instances generated for the node scheduled by hour or minute is generated, the instance generated for the node scheduled by day starts to process and cleanse the output data. |
| The instance generated for a node scheduled by day depends on a specific instance generated for a node scheduled by hour. | If the instance generated for a node scheduled by day on the current day needs to depend on a specific instance generated for a node scheduled by hour or minute on the current day, you can configure the self-dependency for the node scheduled by hour or minute. This way, the scheduling dependencies of the instance generated for the node scheduled by day conform to the principle of scheduling time proximity. This indicates that the current instance depends on the hourly- or minutely-scheduled instance whose scheduling time is the closest to the scheduling time of the current instance. |
Impacts that are generated after you configure the self-dependency for the node scheduled by hour or minute
- Before you configure the self-dependency for the node scheduled by hour or minute, the instances generated for the node in different scheduling cycles do not affect each other.
- After you configure the self-dependency for the node scheduled by hour or minute, the instance generated for the node in the current scheduling cycle can start to run only after the instance generated for the node in the previous scheduling cycle is successfully run. Note After you configure the self-dependency for the node scheduled by hour or minute, the first instance generated for the node on the current day depends on the last instance generated for the same node on the previous day.
Scenario: A node scheduled by day aggregates data generated by a node scheduled by hour
For example, in a business scenario, a node scheduled by day needs to depend on a node scheduled by hour and needs to aggregate data generated by the node scheduled by hour. However, offsets exist in the scheduling parameter configuration of the node scheduled by hour. As a result, the first instance generated for the node scheduled by hour on the current day generates data in the last hourly partition for the previous day. In this case, the instance generated for the node scheduled by day on the current day depends on the first instance generated for the node scheduled by hour on the current day. If you want to enable the node scheduled by day to aggregate data generated by the node scheduled by hour as expected, you can configure the self-dependency for the node scheduled by hour. The following figure shows the configurations. 