When you create a Data Transmission Service (DTS) task to synchronize or migrate data to a Apache Kafka instance, you can select a message acknowledgement mechanism (Ack), which can persistently store messages that are delivered. This topic describes the message acknowledgement mechanisms supported by DTS, including their advantages, disadvantages, and scenarios.
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. |
| 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. Note We recommend that you select this mechanism. |
| 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. |
| This mechanism is applicable if you have high requirements for message reliability, such as financial transactions and order processing. |
Configuration method
Go to the Configure Objects step of a DTS instance for data synchronization or migration, select Message acknowledgement mechanism.