DataWorks:Node freezing and unfreezing

What happens after I freeze or unfreeze an auto triggered node or an auto triggered node instance?

• Freeze or unfreeze an auto triggered node
  Every night, the system generates auto triggered node instances that are scheduled to run on the next day for an auto triggered node. If you freeze the auto triggered node, the auto triggered node instances that are scheduled to run after the time at which you freeze the auto triggered node are also frozen and the descendant instances of the auto triggered node instances cannot be run.

  Note The auto triggered node instances that are scheduled to run on the same day when you freeze the auto triggered node can be run as expected. The auto triggered node instances that are scheduled to run one day later than the day on which you freeze the auto triggered node are frozen and the descendant instances of the auto triggered node instances cannot be run.

  • You can go to the Cycle Task page in Operation Center and perform the operations that are shown in the following figure to freeze and unfreeze auto triggered nodes.
  • You can go to the DataStudio page and configure the Recurrence parameter to freeze or unfreeze an auto triggered node.

  Note In the Schedule section of the Properties tab on the DataStudio page, set the Recurrence parameter to Skip Execution or Normal. Then, commit and deploy the node again. This way, the auto triggered node can be frozen or unfrozen in the production environment.
• Freeze or unfreeze an auto triggered node instance
  The freeze or unfreeze operation on an auto triggered node instance does not have an impact on the status of the auto triggered node to which the instance belongs. If an auto triggered node is frozen and you unfreeze an auto triggered node instance that belongs to the node, other auto triggered node instances that are scheduled to run on the next day are still frozen.

  Notice Freeze and unfreeze operations are manual operations. For any questions, view operation logs.

What happens to data backfill instances and test instances after I freeze an auto triggered node?

A data backfill instance and a test instance are snapshots that are generated for an auto triggered node. If an auto triggered node is frozen, the generated data backfill instance and test instance are also frozen.

How do I rerun an unfrozen auto triggered node instance?

An unfrozen auto triggered node instance is run based on the scheduling time that you specify in the Schedule section of the Properties tab, and the status of the ancestor nodes of the auto triggered node that generates the instance.

For example, Instance a is the ancestor node of Instance b and Instance b is frozen. If you unfreeze Instance b:

• Scenario 1: If Instance a is not run, after Instance b is unfrozen, Instance b is in the Waiting time state and then is run as scheduled.
• Scenario 2: If Instance a is running, after Instance b is unfrozen, Instance b is in the Waiting time state and then is run as scheduled.
• Scenario 3: Instance a is successfully run.
  • If the scheduling time of Instance b does not arrive, Instance b is in the Waiting time state.
  • If the scheduling time of Instance b has elapsed, Instance b fails to be run. If you want to rerun Instance b, click Rerun in the Actions column of Instance b. After Instance b is successfully run, the descendant instances of Instance b are run as scheduled.
• Scenario 4: If Instance a fails to be run, Instance b is not run. For more information about how to troubleshoot an instance that fails to be run, see Nodes that are not run.

Why is a frozen auto triggered node run as scheduled?

• Problem description

  A frozen auto triggered node is run as scheduled.

• Causes and solutions
  Every night, the system generates auto triggered node instances that are scheduled to run on the next day for an auto triggered node and schedules the auto triggered node instances. You can go to the Patch Data or Test Instance page in Operation Center and click Patch Data or Test in the Actions column of the auto triggered node. The system generates a data backfill instance or a test instance based on the snapshot information of the current auto triggered node. You must take note of the following points based on the relationships between auto triggered nodes and auto triggered node instances and between test instances and data backfill instances:

  • Check whether the node that you freeze is an auto triggered node.
  • The freeze operation that is performed on an auto triggered node does not take effect on the auto triggered node instances that are scheduled to run before the time at which you freeze the auto triggered node.
    • The auto triggered node instances that are scheduled to run on the same day when you freeze the auto triggered node can be run as expected.
    • The freeze operation does not take effect on data backfill instances and test instances that are generated before the freeze operation.

How do I view the users who performed operations on a node and view the operations that are performed?

• View the users and operations on the Operation Log tab:
  You can view operation logs on the Operation Log tab of the Cycle Task or Cycle Instance page in Operation Center.
• View the users and operations based on the comparison results of versions of an auto triggered node:

  If you change a node and commit and deploy the node, but the node change operation is not recorded on the Operation Log tab of the Cycle Task or Cycle Instance page in Operation Center, you can compare the current version of the node on the Versions tab of the DataStudio page with the version of the node in the production environment to obtain the details about version changes. For more information, see Versions.

• View the users and operations on the Operating Record page in Operation Center:

  On the Operating Record page, a workspace member who is assigned the O&M or Workspace Manager role can view the operations that are performed by the members in the workspace on pages of Operation Center in the production environment. For more information, see View operation records.