Message acknowledgement mechanism

Name

Description

Advantages and disadvantages

Scenarios

Don't wait for any confirmation

A producer sends a message to a server and does not need to wait for a response from the server. After the message is sent, the producer thinks the message is sent as expected.

• Advantages: High performance and throughput.

• Disadvantages: Low reliability and higher risk of data loss.

This mechanism is applicable if you do not have high requirements for message reliability, such as log collection and monitoring data.

Wait for confirmation from the master node

A producer sends a message to a server and waits for the ackowledgement from leader replica of the server. After the message is sent to the leader replica and written to its local log, the response is returned to the producer.

• Advantages: Applicable to various scenarios.

• Disadvantages: Moderate performance and moderate risk of data loss.

  Data loss may occur in the event of a leader replica (master node) failure.

This mechanism is applicable to most scenarios, especially if you have specific requirements for the message performance and reliability.

Waiting for confirmation of all ISR

A producer sends a message to a server and waits for the ackowledgement from all ISRs (In-Sync Replicas) of the server. After the message is sent to all ISRs and written to its local log, the response is returned to the producer.

• Advantages: High data security.

  Data loss occurs only if all replicas fail.

• Disadvantages: Low performance.

This mechanism is applicable if you have high requirements for message reliability, such as financial transactions and order processing.