[jira] [Resolved] (STORM-810) PartitionManager in storm-kafka should commit latest offset before close

["Jungtaek Lim (JIRA)" <ji...@apache.org>]

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

Jungtaek Lim resolved STORM-810.
--------------------------------
       Resolution: Fixed
    Fix Version/s: 0.11.0

Thanks [~tedxia]

I merged this into master.

I'd like to include this to 0.10.0 again, so I'll merge this to 0.10.x-branch after consensus has been made.

> PartitionManager in storm-kafka should commit latest offset before close 
> -------------------------------------------------------------------------
>
>                 Key: STORM-810
>                 URL: https://issues.apache.org/jira/browse/STORM-810
>             Project: Apache Storm
>          Issue Type: Improvement
>          Components: storm-kafka
>    Affects Versions: 0.10.0, 0.11.0
>            Reporter: xiajun
>            Assignee: xiajun
>             Fix For: 0.11.0
>
>
> When KafkaSpout refresh with kafka partitions, it will remove patitions that no longer served by this spout and close the connection. But before close the connection, PartitionManager don't commit the latest offset. As a result some other spout that serve the removed partition will replay some tuple that between last commit and close.



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