"... since it is no longer fetchable"

[Jon Yeargers <jo...@cedexis.com>]

Attempting to run a KStream app and seeing lots of this sort of error
message:


> Resuming partition <topic>-#
> Pausing partition <topic>-#
> Not returning fetched records for assigned partition <topic>-# since it
is no longer fetchable

This cycles through all the partitions. It seems to get _some_ data from
the topic but clearly it's struggling. I've tried restarting each broker in
sequence and the logs aren't showing anything abnormal.

Using **kafkacat** I can see that there is lots of data available.

Re: "... since it is no longer fetchable"

[Damian Guy <da...@gmail.com>]

Jon,

That is fine. KafkaStreams pauses fetching when its internal buffer is full
and will resume once there is space in the buffer. The "Not returning
fetched..." message will be logged because consumption of that partition
has been paused.

Thanks,
Damian

On Thu, 25 May 2017 at 17:42 Jon Yeargers <jo...@cedexis.com> wrote:

> Attempting to run a KStream app and seeing lots of this sort of error
> message:
>
>
> > Resuming partition <topic>-#
> > Pausing partition <topic>-#
> > Not returning fetched records for assigned partition <topic>-# since it
> is no longer fetchable
>
> This cycles through all the partitions. It seems to get _some_ data from
> the topic but clearly it's struggling. I've tried restarting each broker in
> sequence and the logs aren't showing anything abnormal.
>
> Using **kafkacat** I can see that there is lots of data available.
>