the issue you are facing is not related to that.
>
>
> Best,
> Lisheng
>
>
> sampath kumar 于2019年8月21日周三 下午8:36写道:
>
> > Lisheng ,
> >
> > Issue not with fetch max bytes as same message start processing after
> > restarting the consumer
> >
> &
essage.max.bytes" on broker?
>
> Maybe need you check consumer log to see if can find any clue once you
> enable it. if no any error/exception found on consumer side, maybe need
> change log level to "debug" to get more detail information.
>
> Best,
> Lishen
you configured on consumer and broker?
> you say it will resume when rebalance happen, so consumer is alive, can
> you see any heartbeat information in consumer log?
>
> Best,
> Lisheng
>
>
> sampath kumar 于2019年8月21日周三 下午5:23写道:
>
> > Hi,
> >
> > Using
Hi,
Using Broker 5.3.0, new consumers(Consumers managed by brokers). Brokers
are deployed in a Kubernetes environment
Number of brokers : 3, Number of 3 Zookeeper setup
One of the Topic "inventory.request" we have 3 replication, with insync
replicas configured as 2 and partition count is 1024
W