Hi,

I am talking w.r.t. Kafka 1.0., reducing the poll interval and reducing the
number of records polled are always an option.
I wanted to explore if there are some other options apart from this and in
case of GC pause, both of the above mentioned options will not help.

-Sameer.

On Fri, Jan 26, 2018 at 1:35 AM, R Krishna <krishna...@gmail.com> wrote:

> Think, new versions have better ways of doing this. In 0.10.2, because
> poll() ensure liveness, you can disable auto commits and use consumer
> pause() to avoid calling poll() (so brokers may ignore
> max.poll.interval.ms)
> so those partitions are not assigned to other consumers and also handle
> ConsumerRebalanceListener onPartitionsAssigned or reduce amount of data
> being processed using max.poll.records.
> https://kafka.apache.org/0102/javadoc/org/apache/kafka/clients/consumer/
> KafkaConsumer.html
>
> On Thu, Jan 25, 2018 at 1:27 AM, Sameer Kumar <sam.kum.w...@gmail.com>
> wrote:
>
> > I have a scneario, let say due to GC or any other issue, my consumer
> takes
> > longer than max.poll.interval.ms to process data, what is the
> alternative
> > for preventing the consumer to be marked dead and not shun it out of the
> > consumer group.
> >
> > Though the consumer has not died and session.timeout.ms is being sent at
> > regular intervals in this case.
> >
> > -Sameer.
> >
>
>
>
> --
> Radha Krishna, Proddaturi
> 253-234-5657
>

Reply via email to