[jira] [Updated] (KAFKA-3847) Connect tasks should not share a producer

["Ewen Cheslack-Postava (JIRA)" <ji...@apache.org>]

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

Ewen Cheslack-Postava updated KAFKA-3847:
-----------------------------------------
    Assignee: Liquan Pei  (was: Ewen Cheslack-Postava)

> Connect tasks should not share a producer
> -----------------------------------------
>
>                 Key: KAFKA-3847
>                 URL: https://issues.apache.org/jira/browse/KAFKA-3847
>             Project: Kafka
>          Issue Type: Improvement
>          Components: KafkaConnect
>    Affects Versions: 0.10.0.0
>            Reporter: Ewen Cheslack-Postava
>            Assignee: Liquan Pei
>            Priority: Critical
>             Fix For: 0.10.1.0
>
>
> Currently the tasks share a producer. This is nice in terms of potentially coalescing requests to the same broker, keeping port usage reasonable, minimizing the # of connections to brokers (which is nice for brokers, not so important for connect itself). But it also means we unnecessarily tie tasks to each other in other ways -- e.g. when one needs to flush, it we effectively block it on other connector's data being produced and acked.
> Given that we allocate a consumer per sink, a lot of the arguments for sharing a producer effectively go away. We should decouple the tasks by using a separate producer for each task (or, at a minimum, for each connector's tasks).



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)