[jira] [Updated] (KAFKA-345) Add a listener to ZookeeperConsumerConnector to get notified on rebalance events

["Gwen Shapira (JIRA)" <ji...@apache.org>]

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

Gwen Shapira updated KAFKA-345:
-------------------------------
    Resolution: Fixed
      Assignee: Jiangjie Qin
        Status: Resolved  (was: Patch Available)

Looking at trunk, I think this got in through a different patch... closing this one.

> Add a listener to ZookeeperConsumerConnector to get notified on rebalance events
> --------------------------------------------------------------------------------
>
>                 Key: KAFKA-345
>                 URL: https://issues.apache.org/jira/browse/KAFKA-345
>             Project: Kafka
>          Issue Type: Improvement
>          Components: core
>    Affects Versions: 0.7, 0.8.0
>            Reporter: Peter Romianowski
>            Assignee: Jiangjie Qin
>         Attachments: KAFKA-345.patch, KAFKA-345.patch, KAFKA-345_2014-11-15_01:00:55.patch, KAFKA-345_2014-11-15_01:19:56.patch, KAFKA-345_2014-11-17_17:42:42.patch
>
>
> A sample use-case
> In our scenario we partition events by userid and then apply these to some kind of state machine, that modifies the actual state of a user. So events trigger state transitions. In order to avoid the need of loading user's state upon each event processed, we cache that. But if a user's partition is moved to another consumer and then back to the previous consumer we have stale caches and hell breaks loose. I guess the same kind of problem occurs in other scenarios like counting numbers by user, too.



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