[
https://issues.apache.org/jira/browse/SAMZA-458?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14994670#comment-14994670
]
Ivan Simoneko commented on SAMZA-458:
-------------------------------------
[~navina] [~closeuris] How is it guaranteed that msg2 and msg3 are executed in
the same order as produced? As I see in
org.apache.kafka.clients.producer.internals.RecordAccumulator it uses different
queues for different topic-partition pairs, so if msg2 and msg3 should be
produced to different partitions it could be so that future3 will be done while
future2 is not.
> Close in KafkaSystemProducer should flush all source buffers
> ------------------------------------------------------------
>
> Key: SAMZA-458
> URL: https://issues.apache.org/jira/browse/SAMZA-458
> Project: Samza
> Issue Type: Bug
> Components: kafka
> Reporter: Chris Riccomini
> Assignee: Yan Fang
> Labels: newbie
> Fix For: 0.9.0
>
> Attachments: SAMZA-458.1.patch, SAMZA-458.2.patch, SAMZA-458.3.patch,
> SAMZA-458.patch
>
>
> I noticed that calling KafkaSystemProducer.stop does not flush any
> outstanding messages in the sourceBuffers array. Calling close should flush
> all buffers. Without this, shutting down can cause messages to be dropped.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
