You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@flink.apache.org by "Zhengqi Zhang (Jira)" <ji...@apache.org> on 2022/04/21 09:10:00 UTC
[jira] [Commented] (FLINK-27318) KafkaSink: when init transaction, it take too long to get a producerId with epoch=0
[ https://issues.apache.org/jira/browse/FLINK-27318?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17525568#comment-17525568 ]
Zhengqi Zhang commented on FLINK-27318:
---------------------------------------
[~arvid] it take too long to abort previous transactions.
> KafkaSink: when init transaction, it take too long to get a producerId with epoch=0
> -----------------------------------------------------------------------------------
>
> Key: FLINK-27318
> URL: https://issues.apache.org/jira/browse/FLINK-27318
> Project: Flink
> Issue Type: Bug
> Components: Connectors / Kafka
> Affects Versions: 1.14.4
> Reporter: Zhengqi Zhang
> Priority: Major
> Attachments: image-2022-04-20-17-34-48-207.png, image-2022-04-20-17-59-27-397.png
>
>
> as we can see, the new KafkaSink aborts all transactions that have been created by a subtask in a previous run, only return when get a producerId was unused before(epoch=0). But this can take a long time, especially if the task has been started and cancelled many times before. In my tests, it even took {*}10 minutes{*}. Is there a better way to solve this problem, or {*}do what FlinkKafkaProducer did{*}.
> !image-2022-04-20-17-59-27-397.png|width=534,height=256!
> !image-2022-04-20-17-34-48-207.png|width=556,height=412!
--
This message was sent by Atlassian Jira
(v8.20.7#820007)