Undeploy nodes

Undeploy a node

If you use a standard mode workspace, the development environment is isolated from the production environment. When you delete a node in Data Studio, the node is deleted only from the development environment. To remove the node from the production environment, you must deploy the deletion to the production environment. The node is undeployed only after the deployment succeeds. For more information, see Undeploy a task.

Verify successful undeployment

Restore an undeployed node

After a node is undeployed, it is moved to the Recycle Bin. You can restore the undeployed task from the Recycle Bin. For more information, see Restore a task.

Error: Please deploy the file ${filename} to the production environment or cancel its deployment

• Cause: The Recycle Bin in DataWorks can restore items, such as nodes, resources, or functions, only if they have been deleted from both the development and production environments. This error occurs if an item is deleted from the development environment but this deletion has not been deployed to the production environment.

• Solution: Go to the task deployment page, cancel the deployment for the current task, and then restore the file in Data Studio.

Error: Deletion fails because the node has downstream nodes

• Cause: To ensure the normal execution of downstream tasks, DataWorks allows you to undeploy a task only when the task has no downstream dependencies in both the development and production environments.

  Note

  Undeploying a node may cause other tasks that depend on this node to run abnormally. Communicate with the owners of all tasks that depend on this node before you proceed.

• Solution:

  1. Check the downstream dependencies of the task to be undeployed: Go to the scheduled task page in Operation Center for both the development and production environments, and check whether the task has downstream dependencies. For more information, see View node dependencies.

  2. Remove the downstream dependencies of the task to be undeployed:

     1. Go to the schedule settings page of the downstream dependent task and remove the dependency on the task to be undeployed. For more information, see Delete or change node dependencies.

     2. Submit the downstream task to remove the dependency between the downstream task and the task to be undeployed in the development environment.

     3. Deploy the downstream task to remove the dependency between the downstream task and the task to be undeployed in the production environment.

     4. Continue to undeploy the task. For more information, see Undeploy a task.

Cannot stop historical instances of a deleted node

• Description: After a node in a workflow is deleted and the deletion is deployed to the production environment, the scheduled instances that have already been generated for the node still remain in the production environment. These historical instances may continue to run and trigger timeout alerts. Directly terminating or freezing these instances may fail.

• Solution:

  1. Go to the Operation Center > Scheduled Instances page and search by workflow name or node name to locate the target workflow instance.

  2. Select the target instance and perform the Terminate or Freeze operation. If the workflow contains multiple instances, handle all related instances one by one.

  3. If regular operations do not work, submit a ticket to contact DataWorks technical support for assistance.