Javier,
Got it. The proposal from SO should work, while the drawback is that you
need one more full fledged consumer instance to do that.
If you'd like to go a bit deeper, you can actually turn on DEBUG level
logging on the `o.a.k.clients.NetworkClient` class which would print the
following upon
All right, looks like I was able to reproduce this after all. I believe I
had to restart the producer after changing the offset retention setting in
the broker. Its quite surprising to me that this was the default behavior
before Kafka 2.1.0 -- I imagine quite a few people have been bitten hard by
Hmm, it turns out I was mistaken -- we are running Kafka 2.0.0, not 2.1.0.
We are on 2.1.0 on the client side, not the server.
Reading through KAFKA-4682, am I right in understanding that prior to
2.1.0, the consumer group offsets could be deleted if the consumers are
running, but idle for longer
I did not find anything specific to 2.1.0 to 2.1.1. So I followed the steps
above and it seems to be working fine till now!
On Fri, Feb 22, 2019 at 1:19 PM M. Manna wrote:
> You should follow the guideline added in Kafka.apache.org. It’s listed
> under rolling upgrade section.
>
> I’ve done it r
You should follow the guideline added in Kafka.apache.org. It’s listed
under rolling upgrade section.
I’ve done it recently and it worked fine.
Thanks,
On Fri, 22 Feb 2019 at 07:47, Ankur Rana wrote:
> Hi,
> I'll be upgrading Kafka version from 2.1.0 to 2.1.1. Are there any special
> steps to
