Yes, this is the Jira ticket about this issue: https://issues.apache.org/jira/browse/KAFKA-5600
On Wed, Oct 11, 2017 at 5:47 PM, Vincent Dautremont < vincent.dautrem...@olamobile.com.invalid> wrote: > I would also like to know the related Jira ticket if any, to check that > what I experience the same phenomenon. > I see this happening even without restarting the kafka broker process : > > I sometime have a Zookeeper socket that fails, the Kafka broker then step > down from its leader duties for a few seconds before entering the cluster, > Consumers gets a response from the broker that it is not anymore part of > the cluster. > > So my client resets, gets reassigned partitions and gets some old CG > offsets from day ago (often from log data that was already deleted). > > Thanks. > > > On Wed, Oct 11, 2017 at 1:59 PM, Phil Luckhurst < > phil.luckhu...@encycle.com> > wrote: > > > Upgrading the broker to version 0.11.0.1 has fixed the problem. > > > > Thanks. > > > > -- > The information transmitted is intended only for the person or entity to > which it is addressed and may contain confidential and/or privileged > material. Any review, retransmission, dissemination or other use of, or > taking of any action in reliance upon, this information by persons or > entities other than the intended recipient is prohibited. If you received > this in error, please contact the sender and delete the material from any > computer. >
