You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@kafka.apache.org by "Neha Narkhede (JIRA)" <ji...@apache.org> on 2011/08/23 10:16:28 UTC

[jira] [Updated] (KAFKA-116) AsyncProducer shutdown logic causes data loss

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

Neha Narkhede updated KAFKA-116:
--------------------------------

    Attachment: KAFKA-116.patch

1. Fixed the shutdown bug by setting the closed queue flag before adding the shutdown command to the async producer queue
2. Added more logging at the trace level 
3. Refactored the blocking async producer logic to use case match instead of nested if else

> AsyncProducer shutdown logic causes data loss
> ---------------------------------------------
>
>                 Key: KAFKA-116
>                 URL: https://issues.apache.org/jira/browse/KAFKA-116
>             Project: Kafka
>          Issue Type: Bug
>    Affects Versions: 0.7
>            Reporter: Neha Narkhede
>         Attachments: KAFKA-116.patch
>
>
> The current shutdown logic of the AsyncProducer allows adding events to the queue, after adding the shutdown command to it. The ProducerSendThread drains all the data in the queue until it hits the shutdown command. Hence, all data added after the shutdown command is lost.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira