Kafka Client

Functions

The Kafka Client node is used to send data to Kafka topics.

You can learn more about how to use the Kafka Client node in .

Parameters

Table 1 describes the parameters of the Kafka Client node.

Table 1 Parameters of Kafka Client nodes

Parameter

Mandatory

Description

Data Connection

Yes

Select the MRS Kafka connection created in the management center.

Topic Name

Yes

Select the topic to which data is to be uploaded. If there are multiple partitions, data is sent to partition 0 by default.

Node Name

Yes

Name of a node. The name must contain 1 to 128 characters, including only letters, numbers, underscores (_), hyphens (-), slashes (/), less-than signs (<), and greater-than signs (>).

Text

Yes

Text content sent to Kafka. You can directly enter text or click image2 to use the EL expression.

Table 2 Advanced parameters

Parameter

Mandatory

Description

Max. Node Execution Duration

Yes

Execution timeout interval for the node. If retry is configured and the execution is not complete within the timeout interval, the node will be executed again.

Retry upon Failure

Yes

Whether to re-execute a node if it fails to be executed. Possible values:

  • Yes: The node will be re-executed, and the following parameters must be configured:

    • Retry upon Timeout

    • Maximum Retries

    • Retry Interval (seconds)

  • No: The node will not be re-executed. This is the default setting.

    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.

Policy for Handling Subsequent Nodes If the Current Node Fails

Yes

Operation that will be performed if the node fails to be executed. Possible values:

  • Suspend execution plans of the subsequent nodes: stops running subsequent nodes. The job instance status is Failed.

  • 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 the current job execution plan: If the current job instance is in abnormal state, the subsequent nodes of this node and the subsequent job instances that depend on the current job are in waiting state.

Enable Dry Run

No

If you select this option, the node will not be executed, and a success message will be returned.

last updated: 2025-07-09 16:05 UTC - commit: 61336f3c2e25ce26cb038bce82678d028fe5d438