ogs etc., you've collected if you feel like the above might be what's
> happening.
>
> For clarity, this wouldn't be a correctness problem at all, just a
> misleading
> and troubling log message we shouldn't be producing.
>
> Thanks,
> -John
>
> On Tue,
log
> > > > messages are on WARN level.
> > > >
> > > > If a lot of your records are skipped on app restart with this log
> > > > message on WARN-level, they were also skipped with the log message
on
> > > > DEBUG-level. You simply did no
Hi,
in
https://github.com/apache/kafka/commit/9f5a69a4c2d6ac812ab6134e64839602a0840b87#diff-a5cfe68a5931441eff5f00261653dd10R134
log level of "Skipping record for expired segment" was changed from debug
to warn. Was it intentional change? Should it be somehow handled by user?
How can user handle
Hello,
According to the docs, Kafka Streams tasks pick from the partition with the
smallest timestamp to process the next record.
(
https://kafka.apache.org/documentation/streams/core-concepts#streams_out_of_ordering
)
One can also configure max.task.idle.ms so that Kafka Streams tasks wait
for al
