Help Center> DataArts Studio> User Guide (Kuala Lumpur Region)> User Guide> DataArts Factory> Node Reference> MRS Flink Job
Updated on 2022-12-08 GMT+08:00
View PDF

MRS Flink Job

Function

The MRS Flink node is used to execute predefined Flink jobs in MRS.

Parameters

Table 1 and Table 2 describe the parameters of the MRS Flink node.

Table 1 Parameters of the MRS Flink node

Parameter

Mandatory

Description

Node Name

Yes

Name of the node. The value must consist of 1 to 128 characters and contain only letters, digits, and the following special characters: _-/<>

MRS Cluster Name

Yes

Select the MRS cluster.

To create an MRS cluster, use either of the following methods:
  • Click . On the Clusters page, create an MRS cluster.
  • Go to the MRS console to create an MRS cluster.

Job Name

Yes

Name of an MRS job. The name contains 1 to 64 characters, including only letters, digits, and underscores (_).

NOTE:

The job name cannot contain more than 64 characters. If the job name does not meet requirements, the MRS job will fail to be submitted.

Job Resource Package

Yes

Select a JAR package. Before selecting a JAR package, upload the JAR package to the OBS bucket, create a resource on the Manage Resource page, and add the JAR package to the resource management list. For details, see Creating a Resource.

Job Execution Parameter

No

Key parameter of the program that executes the Flink job. This parameter is specified by a function in the user program. Multiple parameters are separated by space.

Program Parameter

No

Used to configure optimization parameters such as threads, memory, and vCPUs for the job to optimize resource usage and improve job execution performance.

NOTE:

This parameter is mandatory if the cluster version is MRS 1.8.7 or later than MRS 2.0.1.

For details about the program parameters of MRS Flink jobs, see Managing an Existing Cluster > Job Management > Running a Flink Job in the MapReduce Service (MRS) User Guide.

Input Data Path

No

Path where the input data resides.

Output Data Path

No

Path where the output data resides.
Table 2 Advanced parameters

Parameters

Mandatory

Description

Max. Node Execution Duration

Yes

Maximum duration of executing a node. When Retry upon Failure is set to Yes for a node, the node can be re-executed for numerous times upon an execution failure within the maximum duration.

Retry upon Failure

Yes

Whether to re-execute a node after the node fails to be executed.

  • Yes: The node will be re-executed after it fails to be executed. The following parameters must be configured:
    • Maximum Retries
    • Retry Interval (seconds)
  • No: The node will not be re-executed. This is the default setting.
NOTE:

If Max. Node Execution Duration is configured for the node, the node will not be executed again after the execution times out. Instead, the node is set to the failure state.

Failure Policy

Yes

Policies to be performed after the node fails to be executed:

  • End the current job execution plan: stops running the current job. The job instance status is Failed.
  • Go to the next node: ignores the execution failure of the current node. The job instance status is Failure ignored.
  • Suspend current job execution plan: suspends running the current job. The job instance status is Waiting.
  • Suspend execution plans of the subsequent nodes: stops running subsequent nodes. The job instance status is Failed.

Dry run

No

If you select this option, the node will not be executed, and a success message will be returned.
Parent topic: Node Reference