You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@flink.apache.org by "Tzu-Li (Gordon) Tai (JIRA)" <ji...@apache.org> on 2018/05/22 10:22:00 UTC

[jira] [Resolved] (FLINK-9295) FlinkKafkaProducer011 sometimes throws ProducerFencedExceptions when in EXACTLY_ONCE mode

     [ https://issues.apache.org/jira/browse/FLINK-9295?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Tzu-Li (Gordon) Tai resolved FLINK-9295.
----------------------------------------
       Resolution: Fixed
    Fix Version/s:     (was: 1.5.0)
                   1.5.1
                   1.6.0

Merged, via

1.6.0 - 9b7493d143add477fbfd230ea312270b26e45d85
1.5.1 - 9d0cd5848d2eb620263dbb65c8ceb611fa440875

> FlinkKafkaProducer011 sometimes throws ProducerFencedExceptions when in EXACTLY_ONCE mode
> -----------------------------------------------------------------------------------------
>
>                 Key: FLINK-9295
>                 URL: https://issues.apache.org/jira/browse/FLINK-9295
>             Project: Flink
>          Issue Type: Bug
>          Components: Kafka Connector
>    Affects Versions: 1.4.2
>            Reporter: Christopher Ng
>            Assignee: Piotr Nowojski
>            Priority: Major
>             Fix For: 1.6.0, 1.5.1
>
>
> {{FlinkKafkaProducer011}} can throw {{ProducerFencedExceptions}} if multiple sinks are used within the same sub-task.  This can happen when operator-chaining results in two different sinks in the same topology being chained into a task, and thus into each of its sub-tasks.
> The problem is that {{TransactionIdsGenerator}} only takes into account the task name, the subtask index, the number of subtasks, and a couple of other things.  All the attributes are the same between different {{FlinkKafkaProducer011s}} within the same sub-task, so they get the same transaction ids and one of them ends up failing.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)