Mailing-List: contact kafka-dev-help@incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: kafka-dev@incubator.apache.org
Date: Sun, 3 Jun 2012 22:45:23 +0000 (UTC)
From: "Jun Rao (JIRA)" <jira@apache.org>
To: kafka-dev@incubator.apache.org
Message-ID: <1421406864.32352.1338763523027.JavaMail.jiratomcat@issues-vm>
In-Reply-To: 
 <993321755.14184.1337351708005.JavaMail.tomcat@hel.zones.apache.org>
Subject: [jira] [Commented] (KAFKA-345) Add a listener to
 ZookeeperConsumerConnector to get notified on rebalance events
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


    [ https://issues.apache.org/jira/browse/KAFKA-345?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13288276#comment-13288276 ] 

Jun Rao commented on KAFKA-345:
-------------------------------

Peter,

Regarding #2, naming it as ConsumerListener is fine.
                
> 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
>            Reporter: Peter Romianowski
>         Attachments: KAFKA-345.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 is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira