You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@kafka.apache.org by "Rajini Sivaram (JIRA)" <ji...@apache.org> on 2016/11/02 11:37:59 UTC

[jira] [Updated] (KAFKA-3703) Handle close gracefully for consumers and producers with acks=0

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

Rajini Sivaram updated KAFKA-3703:
----------------------------------
    Summary: Handle close gracefully for consumers and producers with acks=0  (was: Selector.close() doesn't complete outgoing writes)

> Handle close gracefully for consumers and producers with acks=0
> ---------------------------------------------------------------
>
>                 Key: KAFKA-3703
>                 URL: https://issues.apache.org/jira/browse/KAFKA-3703
>             Project: Kafka
>          Issue Type: Bug
>          Components: clients
>    Affects Versions: 0.10.0.1
>            Reporter: Rajini Sivaram
>            Assignee: Rajini Sivaram
>
> Outgoing writes may be discarded when a connection is closed. For instance, when running a producer with acks=0, a producer that writes data and closes the producer would expect to see all writes to complete if there are no errors. But close() simply closes the channel and socket which could result in outgoing data being discarded.
> This is also an issue in consumers which use commitAsync to commit offsets. Closing the consumer may result in commits being discarded because writes have not completed before close().



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