We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
adapter大致的调度结构:
canalMsgConsumer.connect(); while (running) { for (int i = 0; i < retry; i++) { canalMsgConsumer.getMessage() ; canalMsgConsumer.ack / rollback(); } } canalMsgConsumer.disconnect();
这里会在adapter running退出时执行disconnect逻辑,目前部分的connector组件的disconnect逻辑有unsubscribe的行为 比如,以CanalTCPConsumer为例:
public void disconnect() { canalConnector.unsubscribe(); canalConnector.disconnect(); } } tcp模式下unsubscribe发送给canal-server,会导致清理cursor位点,如果此时canal-server出现重启,就会从最新的binlog开始消费,从而binlog出现数据丢失的风险
The text was updated successfully, but these errors were encountered:
fixed issue #4864 , connector.disconnect optimize
34e9440
kafka/rocketmq,在disconnect后还能继续保持上一个位点继续消费,暂时不影响
Sorry, something went wrong.
fixed issue alibaba#4864 , connector.disconnect optimize
905325a
No branches or pull requests
adapter大致的调度结构:
这里会在adapter running退出时执行disconnect逻辑,目前部分的connector组件的disconnect逻辑有unsubscribe的行为
比如,以CanalTCPConsumer为例:
The text was updated successfully, but these errors were encountered: