Zero-load node

Updated at:

A zero-load node is a control node that produces no data. When scheduled, it immediately returns a success result without running a task, consuming resources, or blocking downstream nodes. It is commonly used as the orchestration start node for a workflow or as an output node that combines multiple branches. This topic describes its use cases and how to create and use it.

Use cases

Zero-load nodes are commonly used in the following scenarios:

  • Manage workflows with complex dependencies

    If your business contains multiple workflows, we recommend that you add a zero-load orchestration start node to each workflow. This makes the data flow between workflows easier to manage and understand.Workflow management

  • Schedule nodes with no lineage relationship

    If the final output of a workflow has multiple input branches that do not depend on one another, set a zero-load node as the upstream node of those inputs and the workspace root node as the upstream node of the zero-load node. The workspace root node then schedules the zero-load node, which schedules the downstream business nodes. If the whole workflow requires a unified schedule, you can also set the zero-load node's scheduled time to control the earliest time at which each branch can run.

    Note

    When the workspace root node is used as an upstream dependency, it does not appear in the workflow panel. After you submit and publish the task, you can view it in Operation Center. For more information about Operation Center, see Basic O&M operations for recurring tasks.

    Example:Schedule nodes without lineage dependenciesoss_data_sync_dqc and rds_data_sync_dqc have no lineage relationship, so you cannot set their scheduling dependency based on lineage. In this case, use a zero-load node (workshop_start_dqc) as the orchestration start node to schedule the independent downstream branches. Each branch starts when its run conditions are met.

    Note

    When you synchronize data from other data sources into DataWorks through offline synchronization, the receiving tables have no upstream lineage on the DataWorks side.

  • Manage workflows with multiple branch results and configure scheduling dependencies across workflows

    To make a workflow with multiple branch results depend on another workflow, use a zero-load node to combine the branches. Then manually use that node's output as an input to the downstream workflow's orchestration start node. For more information, see Configure scheduling dependencies across workflows.

    Note

    When a workflow has multiple branch results, create a zero-load node, such as workflow_end_zero_load_node, that depends on all of those branches. A successful run of workflow_end_zero_load_node indicates that the workflow has completed.

Create and use a zero-load node

  1. Go to the Data Development page.

    Log on to the DataWorks console. In the target region, click Data Development and O&M > Data Development in the left-side navigation pane. Select a workspace from the drop-down list and click Go to Data Development.

  2. Create a Workflow.

    If you have an existing Workflow, skip this step.

    1. Hover over the 新建 icon and select Create Workflow.

    2. In the Create Workflow dialog box, enter a Workflow Name.

    3. Click Create.

  3. Create a zero-load node.

    1. Move the pointer over the image.png icon and select Create Node > General > Zero-Load Node.

      Alternatively, find the relevant workflow, right-click it, and select Create Node > General > Zero-Load Node.

    2. In the Create Node dialog box, enter the Name and select the Node Type and Path.

      Note

      A node name can contain uppercase and lowercase letters, Chinese characters, digits, underscores (_), and periods (.). It cannot exceed 128 characters.

    3. Click OK to open the zero-load node editor.

  4. Configure task scheduling.

    If the node must run periodically, click Scheduling Settings on the right side of the node editor and configure its scheduling information based on your business needs:

  5. Commit and deploy the task.

    1. In the toolbar, click the 保存 icon to save the node.

    2. In the toolbar, click the 提交 icon to commit the task.

    3. In the Commit Node dialog box, enter a Change Description.

    4. Click Determine.

    In a standard mode workspace, you must deploy the task to the production environment after you commit it. In the top menu bar, click Deploy. For more information, see Deploy tasks.

  6. View scheduled tasks.

    1. In the upper-right corner of the editor, click O&M Personnel to open the production environment's Operation Center.

    2. View the scheduled tasks that are running. For more information, see Manage scheduled tasks.

    To view more details about scheduled tasks, click Operation Center in the top menu bar. For more information, see Operation Center overview.