Details
-
Improvement
-
Status: Resolved
-
Major
-
Resolution: Fixed
-
0.7, 0.8.0
-
None
-
None
Description
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.
Attachments
Attachments
Issue Links
- is depended upon by
-
KAFKA-346 Don't call commitOffsets() during rebalance
- Resolved