What you are talking about is manual partition assignment, which is
different than reassignment upon rebalancing.
Consumer informs group coordinator that close() is invoked and that would
eventually cause rebalancing. I believe what you are talking about is the
rebalance listener.
On 1 Jun 2018 0
Do you want to avoid rebalancing in such way that if a consumer exits then
its previously owned partition should be left disowned? But then who will
consume from partition that was deserted by a exiting consumer? In such
case you can go for manual partition assignment. Then there is no question
of
Hello,
We are trying to move from single partition to multi-partition approach for
our topics. The purpose is:
1) Each production/testbed server will have a non-Daemon thread (consumer)
running.
2) It will consume messages, commit offset (manual), and determine next
steps if commit fails, app fai
