Hello Henry, I saw your detailed explanations on the JIRA ticket.
Thinking about this a bit more, I think moving the start offset should be
as important as an event as truncating log tail, or rolling new segment etc
(their log4j levels are all INFO). But I also agree that with the streams
periodic
On server side, we use INFO for everything.
Log4j setting can be a temporary hack, but we would like to keep INFO
logging as the default.
I think those two logging lines can be just downgraded into DEBUG loggings,
moving start offset is not that eventful to be logged as INFO.
On Fri, Jul 6, 2018
Hello Henry,
What's your server-side log4j settings? Could you use WARN on these two
classes: kafka.server.epoch.LeaderEpochFileCache and kafka.log.Log.
Guozhang
On Fri, Jul 6, 2018 at 3:08 PM, Henry Cai
wrote:
> @guozhang
>
> After we moved to kafka-1.1.0 for our Kafka streams application,
@guozhang
After we moved to kafka-1.1.0 for our Kafka streams application, our broker
logs are polluted with loggings such as:
[2018-07-06 21:59:26,170] INFO Cleared earliest 0 entries from epoch cache
based on passed offset 301483601 leaving 1 in EpochFile for partition
inflight_spend_unified_st
