A SHELL node is used to execute a custom Shell script. This topic describes the parameters that are involved when you create a SHELL node.
The name of the node. A node name is unique in a workflow.
The feature description of the node.
The priority of the node in the workflow. Default value: MEDIUM. Valid values:
Number of failed retries
The maximum number of times that the system automatically retries to run the node if the workflow fails.
Failed retry interval
The interval between two consecutive retries. Unit: minutes.
Delay execution time
The amount of time that is delayed before the node is run. The default value is 0, which indicates that the node is immediately run after it is created. The node is delayed to be run only if you specify a value that is greater than 0 for this parameter. Unit: minutes.
Specifies whether to enable alerting on node execution timeout. By default, the Timeout alarm switch is turned off. You can turn on the Timeout alarm switch and select Timeout alarm and Timeout failure as Timeout strategy. If the execution of a node exceeds the timeout period, an alert message is sent to your mailbox, and the node fails.
Submit on Yarn
Specifies whether to submit the node to YARN of an EMR cluster for execution. If you turn on the Submit on Yarn switch, the node is submitted to YARN of an EMR cluster for execution. This directly affects the files and environment of the EMR cluster. Proceed with caution.
By default, the Submit on Yarn switch is turned off. If you turn on this switch, you can configure the following parameters:
The custom Shell program.
The resource files that are required for node execution. If a resource file is referenced by other parameters, make sure that you created or uploaded the file on the File Manage page of the Resources tab and select the file as Resources.
The custom parameters of the node. The custom parameters are used to replace
The ancestor node of the node.