Re: After upgrade to 2.13 2.8.1 getting message in log

I see what the issue is – trying to resolve – looking at the consumer offset’s, the ones that are logging this message are all not in sync for this broker. I read that setting this parameter - replica.lag.time.max.ms , to a time before the failure may allow for the consumer offset to get back in

Re: After upgrade to 2.13 2.8.1 getting message in log

Hi Jim, Thanks for reporting the issue. Could you file a jire bug here ? > I have found several blogs/user group references to the message but none have successfully stop the message Could you share these ref

After upgrade to 2.13 2.8.1 getting message in log

Hi all , after upgrading to 2.8.1 and restarting the brokers, one of the brokers is continually logging messages similar to this Feb 25 23:58:17 bigdata-worker2.dc.res0.local WARN: (Logging.scala:70) [ReplicaFetcher replicaId=2, leaderId=0, fetcherId=0] Reset fetch offset for partition __consu