After you configure scheduling dependencies for an auto triggered node, you can preview the scheduling dependencies of the auto triggered node and view the estimated execution time of instances that are generated for the auto triggered node within scheduling days. This preview feature helps you determine whether the scheduling dependencies meet your expectations, and ensures that the auto triggered node can be scheduled as expected. If the scheduling dependencies do not meet your expectations, we recommend that you modify the scheduling configurations at the earliest opportunity to prevent the running of the auto triggered node from being delayed.
Precautions
The number of scheduling cycles of an ancestor node may be different from that of a descendant node, and the scheduling dependencies between the ancestor and descendant instances may vary for different scheduling cycles. If the number of scheduling cycles and the scheduling time between the ancestor and descendant instances of a node are inconsistent, we recommend that you preview the scheduling dependencies between ancestor and descendant instances before you deploy the node. This ensures that the configured scheduling dependencies meet your expectations. For information about the principles for configuring scheduling dependencies and sample scheduling dependencies in special dependency scenarios, see Principles and samples of scheduling configurations in complex dependency scenarios.
A directed acyclic graph (DAG) that is generated based on scheduling dependencies is only for reference and may be different from the DAG in the production environment.
NoteIf you change the scheduling cycle of a node in the production environment, you must set the Instance Generation Mode parameter to Immediately After Deployment for the node and deploy the node. In this case, the instances that have been generated for the node and are scheduled to run on the current day may be replaced, and you cannot preview the actual scheduling dependencies of the instances on the current day. For information about the modes in which instances take effect, see Configure immediate instance generation for a task.
You can preview only the ancestor and descendant nodes that are at the nearest level of the current node.
To ensure that the scheduling dependencies of the current node are correct, confirm that ancestor nodes of the current node are saved.
In the DAG of a node, solid lines indicate same-cycle scheduling dependencies and dashed lines indicate cross-cycle scheduling dependencies, which refer to dependencies on instances of the previous cycle.
Description of the DAG of a node
DataWorks provides the following methods that you can use to preview the scheduling dependencies of a node: Not Aggregate, Aggregate By Workspace, and Aggregate By Owner. You can select a method based on your business requirements. For more information, see Appendix: Use the features provided in a DAG.
When you preview the scheduling dependencies of a node, solid lines indicate same-cycle scheduling dependencies and dashed lines indicate cross-cycle scheduling dependencies, which refer to dependencies on instances of the previous cycle.
The following figures show preview effects by using different aggregation methods on the Node Dependency tab.
Preview scheduling dependencies of a node
DataWorks generates a DAG for a node based on the scheduling dependency configurations of the node. You can check whether the scheduling dependency configurations of the node meet your expectations based on the DAG.
You can click a node to view the details of the node.
Preview scheduling dependencies of an instance
If an auto triggered node generates multiple instances on a scheduling day, DataWorks generates scheduling dependencies and estimated execution time for all the instances based on the scheduling dependency configurations and time configurations of the node. You can check whether the scheduling dependencies and execution time of each instance in each cycle meet your expectations.
You can click an instance to view the details of the instance.
If a point in time that is accurate to the hour or minute is specified for a node scheduled by hour or minute, the scheduling parameters of the node are replaced based on the scheduling time of the instance that is generated for the node in each scheduling cycle. For example, you assign $[hh24] to a scheduling parameter for a node. The scheduling parameter of the instance that is generated for the node in each cycle is replaced by the scheduling time of the instance. For more information, see Appendix: Relationships between scheduling parameters and the data timestamp, scheduling time, and actual running time of a node.
