[jira] [Resolved] (STORM-2361) Kafka spout - after leader change, it stops committing offsets to ZK

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

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

Jungtaek Lim resolved STORM-2361.
---------------------------------
       Resolution: Fixed
         Assignee: Ernestas Vaiciukevičius
    Fix Version/s: 1.0.4
                   1.1.0
                   2.0.0

Thanks [~ernisv], I merged into master, 1.x, 1.0.x branches.

> Kafka spout - after leader change, it stops committing offsets to ZK
> --------------------------------------------------------------------
>
>                 Key: STORM-2361
>                 URL: https://issues.apache.org/jira/browse/STORM-2361
>             Project: Apache Storm
>          Issue Type: Bug
>          Components: storm-kafka
>    Affects Versions: 1.1.0
>            Reporter: Ernestas Vaiciukevičius
>            Assignee: Ernestas Vaiciukevičius
>             Fix For: 2.0.0, 1.1.0, 1.0.4
>
>          Time Spent: 1h 40m
>  Remaining Estimate: 0h
>
> After STORM-2296 although Kafka spouts do not generate duplicates, the offsets committment to ZK may stop on recreated PartitionManagers.
> This is because ack's for messages emitted by already destroyed PartitionManagers are not routed properly to the new PartitionManagers handling that partition.
> E.g: 
> {code:java} public void ack(Object msgId) {
>         KafkaMessageId id = (KafkaMessageId) msgId;
>         PartitionManager m = _coordinator.getManager(id.partition);
>         if (m != null) {
>             m.ack(id.offset);
>         }
> {code}
> id.partition is Partition(host, partition, topic), which is different if Kafka broker changed.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)