Ted

I don't see any other INFO log messages so I assume that means it is the
DEBUG case I'm seeing?

I don't have DEBUG enabled at the moment.

Thanks

On Wed, 13 Jun 2018, 00:21 Ted Yu, <yuzhih...@gmail.com> wrote:

> Before Errors.INVALID_FETCH_SESSION_EPOCH is returned, FetchSession.scala
> would log the reason for the response.
> There are 3 cases, 2 with info log and 1 with debug log.
> Here is one code snippet:
>
>             if (session.epoch != reqMetadata.epoch()) {
>
>               debug(s"Created a new error FetchContext for session id ${
> session.id}: expected " +
>
>                 s"epoch ${session.epoch}, but got epoch $
> {reqMetadata.epoch()}.")
>
>               new SessionErrorContext(Errors.INVALID_FETCH_SESSION_EPOCH,
> reqMetadata)
>
> Can you pastebin the log line preceding what you pasted ?
>
> Thanks
>
> On Tue, Jun 12, 2018 at 3:12 PM, Mark Anderson <manderso...@gmail.com>
> wrote:
>
> > We recently updated our Kafka brokers and clients to 1.1.0. Since the
> > upgrade we periodically see INFO log entries such as
> >
> > INFO Jun 08 08:30:20.335 61161458 [KafkaRecordConsumer-0]
> > org.apache.kafka.clients.FetchSessionHandler [Consumer
> > clientId=consumer-1,
> > groupId=group_60_10] Node 3 was unable to process the fetch request with
> > (sessionId=819759315, epoch=145991): INVALID_FETCH_SESSION_EPOCH.
> >
> > I see that this message comes from the changes introduced in KIP-227:
> > Introduce Incremental FetchRequests To Increase Partition Stability
> > <https://cwiki.apache.org/confluence/display/KAFKA/KIP-
> > 227%3A+Introduce+Incremental+FetchRequests+to+Increase+
> > Partition+Scalability>.
> > However, I cannot find any detailed information about why this message
> > would appear or what parameters might have to be tuned after its
> > introduction.
> >
> > So far it doesn't seem to have an impact on consumer behaviour with
> respect
> > to receiving records but I would like to understand
> >
> >    1. Why is the message being logged?
> >    2. Do I need to do anything?
> >    3. Can anything be done to stop it being logged?
> >
> > Thanks,
> > Mark
> >
>

Reply via email to