DataWorks:Configure time properties

The time properties of a node define only the time when you want to schedule the node. Whether the node is run and the actual time when the node is run are determined by multiple factors. The factors include but are not limited to the following items:

• Control of the scheduling switch

  The node can be automatically scheduled based on its scheduling properties only if Periodic scheduling is turned on for the workspace to which the node belongs. You can turn on the switch on the Scheduling Settings tab of the Settings page in DataStudio for a workspace. For more information, see Configure scheduling settings.

• Impacts of scheduling dependencies of the node on the node execution time

  The scheduling time that you specify for a node takes effect only on the node. The actual time at which the node is run is related to the scheduling time of the ancestor nodes of the node. The node can start to run only if the scheduling time of the ancestor nodes arrives and the ancestor nodes are successfully run. The same logic applies to a node whose scheduling time is earlier than the scheduling time of the ancestor nodes of the node. For more information, see Impacts of dependencies between nodes on the running of the nodes.

• Impacts of resource groups required to run the node on the node execution time

  The running of the node is determined by not only the scheduling time of the ancestor nodes of the node and whether the ancestor nodes are successfully run, but also the resource groups that are required to run the node. Whether the resources that are required to run the node are sufficient at the scheduling time of the node also affects the running of the node. For more information, see Node execution mechanisms.

• Impacts of environments

  Only nodes that are deployed to the production environment can be automatically scheduled to run. If you want nodes to be periodically scheduled, you must deploy the nodes to the production environment. Nodes in the development environment cannot be automatically scheduled.

• Ways in which the node is run

  In DataWorks, an auto triggered node generates instances based on the scheduling frequency and the number of scheduling cycles of the node. For example, the number of instances generated for a node scheduled by hour every day is the same as the number of scheduling cycles of the node every day. The node is run as an instance.

• Scheduling time

  During peak hours such as early mornings, all nodes (including the root node of the current workspace) for which the scheduling time is set to 00:00 will be scheduled to run within the time range from 00:00 to 00:05.

The following table describes the valid values of the Recurrence parameter.

The scheduling frequency of a node determines the number of cycles that the node is automatically run in the scheduling scenario. A scheduling frequency is used to define the interval at which the code logic of a node is actually executed in the scheduling system in the production environment. The node generates instances based on the scheduling frequency and the number of scheduling cycles of the node. For example, the number of instances generated for a node scheduled by hour every day is the same as the number of scheduling cycles of the node every day. The node is run as an instance.

The following table describes the valid values of the Scheduling Cycle parameter.

You can use the Timeout definition parameter to specify a timeout period for a node. If the period of time for which the node is run exceeds the specified timeout period, the node fails. Take note of the following items when you use this parameter:

• The timeout period applies to auto triggered node instances, data backfill instances, and test instances.

• The default timeout period ranges from 72 hours to 168 hours. The system automatically adjusts the default timeout period for a node based on system loads.

• You can customize a timeout period, but it cannot exceed 168 hours.

In the Schedule section, you can configure the conditions, interval, and number of times for rerunning a node.

• Rerun

  The following table describes the valid values of the Rerun parameter.

  Note

  You can click Modify Default Settings next to the Rerun parameter to go to the Scheduling Settings tab.

  Value	Scenario
  Allow Regardless of Running Status	If the data idempotence of a node is not affected after the node is rerun multiple times, you can set the Rerun parameter to this value.
  Allow upon Failure Only	If the rerun of a failed node does not affect the data idempotence but the rerun of a successful node does, you can set the Rerun parameter to this value.
  Disallow Regardless of Running Status	If the data idempotence of a node cannot be ensured after the node is rerun, you can set the Rerun parameter to this value. Note If you set the Rerun parameter to Disallow Regardless of Running Status, the system does not automatically rerun the node after the system recovers from an exception. The Auto Rerun upon Failure parameter is not displayed if you set the Rerun parameter to Disallow Regardless of Running Status.

• Auto Rerun upon Failure

  The following table describes the parameters you must configure if you allow automatic reruns after an error occurs.

  Parameter	Description
  Number of re-runs	The default number of times that an auto triggered node is rerun after it fails to run as scheduled. Valid values: 1 to 10. The value 1 indicates that the node is rerun once after it fails to run as expected. The value 10 indicates that the node is rerun ten times after it fails to run as expected. You can configure this parameter based on your business requirements.
  Rerun interval	The interval at which a node is rerun after it fails to run as scheduled. You can configure this parameter based on your requirements. Valid values: 1 to 30. Default value: 30. Unit: minutes.

  Note

  • The Auto Rerun upon Failure parameter is not displayed if you set the Rerun parameter to Disallow Regardless of Running Status. In this case, the node is not allowed to rerun after it fails to run as scheduled.

  • You can specify the default number of reruns and default rerun interval for the nodes in a workspace on the Scheduling Settings tab. For more information, see Configure scheduling settings.

  • The automatic rerun feature does not take effect if a node fails because the timeout period is exceeded.

For a node that is scheduled by week, month, or year, the scheduling system runs the node at the scheduling time every day. On the days that are not specified to run the node, a dry run is performed on the node and the node generates no data. The following descriptions provide the effects of a dry run:

• The scheduling system directly returns a success response, and the running duration is 0 second.

• No run logs are generated.

• The running of descendant nodes is not affected.

• No resources are occupied.