Developing a Real-Time Processing Single-Task MRS Flink Jar Job
Prerequisites
A single-task real-time processing Flink Jar job has been created. For details, see Creating a Job.
Configuring the MRS Flink Jar Job
Parameter |
Mandatory |
Description |
---|---|---|
Flink Job Name |
Yes |
Enter the Flink job name. The name is automatically generated in Workspace-Job name format. The job name can contain 1 to 64 characters. Only letters, digits, hyphens (-), and underscores (_) are allowed. Chinese characters are not allowed. |
MRS Cluster |
Yes |
Select an MRS cluster.
NOTE:
Currently, jobs with a single Flink Jar node support MRS 3.2.0-LTS.1 and later versions. |
Program Parameter |
No |
Set job running parameters. This parameter is displayed only after an MRS cluster is selected. (Optional) Configure optimization parameters such as threads, memory, and vCPUs for the job to optimize resource usage and improve job execution performance.
CAUTION:
You can query historical checkpoints and select a specified checkpoint to start a Flink JAR job. To make a Flink checkpoint take effect, configure the following two parameters:
NOTE:
This parameter is mandatory if the cluster version is MRS 1.8.7 or later than MRS 2.0.1. Click Select Template and select a parameter template. You can also select multiple templates. For details on how to create data connections, see Configuring a Template. For details about the program parameters of MRS Spark jobs, see Running a Flink Job in the MapReduce Service User Guide. |
Job Execution Parameter |
No |
Set the parameters for the Flink job. Variables required for executing the Flink job. These variables are specified by the functions in the Hive script. Multiple parameters are separated by spaces. |
MRS Resource Queue |
No |
Select a created MRS resource queue. Select a queue you configured in the queue permissions of DataArts Security. If you set multiple resource queues for this node, the resource queue you select here has the highest priority. |
Flink 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. |
Rerun Policy |
No |
|
Input Data Path |
No |
Set the input data path. You can select an HDFS or OBS path. |
Output Data Path |
No |
Set the output data path. You can select an HDFS or OBS path. |
Parameter |
Mandatory |
Description |
---|---|---|
Job Status Polling Interval (s) |
Yes |
Set the interval at which the system checks whether the job is complete. The interval can range from 30s to 60s, or 120s, 180s, 240s, or 300s. During job execution, the system checks the job status at the configured interval. |
Maximum Wait Time |
Yes |
Set the timeout interval for the job. If the job is not complete within the timeout interval and retry is enabled, the job will be executed again.
NOTE:
If the job is in starting state and fails to start, it will fail upon timeout. |
Retry upon Failure |
No |
Whether to re-execute a node if it fails to be executed.
NOTE:
If retry is configured for a job node and the timeout duration is configured, the system allows you to retry a node when the node execution times out. If a node is not re-executed when it fails upon timeout, you can go to the Default Configuration page to modify this policy. Retry upon Timeout is displayed only when Retry upon Failure is set to Yes. |
After setting the parameters, click Save and submit the job.
Click Start to run the job.
Configuring Basic Job Information
Parameter |
Description |
---|---|
Owner |
An owner configured during job creation is automatically matched. This parameter value can be modified. |
Job Agency |
This parameter is available when Scheduling Identities is set to Yes. After an agency is configured, the job interacts with other services as an agency during job execution. |
Priority |
Priority configured during job creation is automatically matched. This parameter value can be modified. |
Execution Timeout |
Timeout of the job instance. If this parameter is set to 0 or is not set, this parameter does not take effect. If the notification function is enabled for the job and the execution time of the job instance exceeds the preset value, the system sends a specified notification, and the job keeps running. |
Exclude Waiting Time from Instance Timeout Duration |
Whether to exclude the wait time from the instance execution timeout duration If you select this option, the time to wait before an instance starts running is excluded from the timeout duration. You can modify this setting on the Default Configuration page. If you do not select this option, the time to wait before an instance starts running is included in the timeout duration. |
Custom Parameter |
Set the name and value of the parameter. |
Job Tag |
Configure job tags to manage jobs by category. Click Add to add a tag to the job. You can also select a tag configured in Managing Job Tags. |
Configuring Job Parameters
Click Parameters on the right of the editor and set the parameters described in Table 4.
Function |
Description |
---|---|
Variables |
|
Add |
Click Add and enter the variable parameter name and parameter value in the text boxes.
After the parameter is configured, it is referenced in the format of ${parameter name} in the job. |
Edit Parameter Expression |
Click next to the parameter value text box. In the displayed dialog box, edit the parameter expression. For more expressions, see Expression Overview. |
Modify |
Change the parameter name or value in the corresponding text boxes. |
Mask |
If the parameter value is a key, click to mask the value for security purposes. |
Delete |
Click next to the parameter name and value text boxes to delete the job parameter. |
Constant Parameter |
|
Add |
Click Add and enter the constant parameter name and parameter value in the text boxes.
After the parameter is configured, it is referenced in the format of ${parameter name} in the job. |
Edit Parameter Expression |
Click next to the parameter value text box. In the displayed dialog box, edit the parameter expression. For more expressions, see Expression Overview. |
Modify |
Modify the parameter name and parameter value in text boxes and save the modifications. |
Delete |
Click next to the parameter name and value text boxes to delete the job parameter. |
Workspace Environment Variables |
|
View the variables and constants that have been configured in the workspace. |
Click the Parameter Preview tab and configure the parameters listed in Table 5.
Function |
Description |
---|---|
Current Time |
This parameter is displayed only when Scheduling Type is set to Run once. The default value is the current time. |
Event Triggering Time |
This parameter is displayed only when Scheduling Type is set to Event-based. The default value is the time when an event is triggered. |
Scheduling Period |
This parameter is displayed only when Scheduling Type is set to Run periodically. The default value is the scheduling period. |
Start Time |
This parameter is displayed only when Scheduling Type is set to Run periodically. The value is the configured job execution time. |
Start Time |
This parameter is displayed only when Scheduling Type is set to Run periodically. The value is the time when the periodic job scheduling starts. |
Subsequent Instances |
Number of job instances scheduled.
|
In Parameter Preview, if a job parameter has a syntax error, the system displays a message.
If a parameter depends on the data generated during job execution, such data cannot be simulated and displayed in Parameter Preview.
Feedback
Was this page helpful?
Provide feedbackThank you very much for your feedback. We will continue working to improve the documentation.See the reply and handling status in My Cloud VOC.
For any further questions, feel free to contact us through the chatbot.
Chatbot