DataWorks:Node undeployment

How do I undeploy a node?

If you use a workspace in standard mode, data is isolated between the development and production environments. If you delete a node on the DataStudio page in the DataWorks console, the node is deleted only from the development environment. To delete the node from the production environment, you must deploy the deletion operation to the production environment. This way, the node is undeployed from the production environment. For more information, see Bring a node offline.

How do I check whether a node is undeployed from the production environment?

After you undeploy a node, you can go to the Cycle Task page in Operation Center to check whether the node exists. If the node does not exist, the node is undeployed.

How do I restore an undeployed node?

After you undeploy a node, the node is moved to the recycle bin. You can restore the undeployed node from the recycle bin. For more information, see Bring a node offline.

Error: The ${filename} file is not deployed to the production environment or the node deletion operation is being deployed on the Deploy page

• Cause: The recycle bin in the DataWorks console allows you to restore only objects such as nodes, resources, and functions that are deleted from both the development and production environments. If a node is deleted only from the development environment and the deletion operation is not deployed to the production environment, the error is reported.
• Solution: Go to the Deploy page to cancel the node deletion operation, and then restore the data development file.

Error: The node fails to be deleted or undeployed because the node has descendant nodes.

• Cause: To ensure that descendant nodes of a node can be normally run, DataWorks allows you to undeploy only nodes that do not have descendant nodes in both the development and production environments.
  Note If you undeploy a node that has descendant nodes, exceptions may occur on the descendant nodes. We recommend that you contact the owner of each descendant node before you undeploy the current node.
• Solution:
  1. Check whether a node that you want to undeploy has descendant nodes: You can go to the Cycle Task pages in Operation Center in the development and production environments to check whether the node that you want to undeploy has descendant nodes. For more information, see View the DAG of an auto triggered node.
  2. Remove scheduling dependencies between the current node and its descendant nodes:
     1. Go to the Properties tab of the descendant nodes and remove the scheduling dependencies of the descendant nodes on the node that you want to undeploy. For more information, see Delete or change scheduling dependencies between nodes.
     2. Commit the descendant nodes to remove the scheduling dependencies of the descendant nodes on the node that you want to undeploy in the development environment.
     3. Deploy the descendant nodes to remove the scheduling dependencies of the descendant nodes on the node that you want to undeploy in the production environment.
     4. Continue to undeploy the node. For more information, see Bring a node offline.