Hi, we are running a 0.10.1.1 Kafka cluster with 2 brokers and recently encountered an issue with partition offsets.
Our application relies on saving the offsets for each partition in order to be able to replay the events that occurred after a certain point in time. The issue is that we found ourselves in a situation where our saved offsets where ahead of the current ones. Did anyone face a similar issue or knows why can it occur? Broker config: retention.ms=7884000000 log.segment.bytes=1073741824 log.retention.check.interval.ms=300000. In the broker logs, I could see these messages, but I believe it is normal operation: [2017-05-08 08:32:11,673] INFO Truncating log person-babel-updated-3 to offset 90727. (kafka.log.Log) [2017-05-08 08:32:11,676] INFO Truncating log company-updated-11 to offset 1022986. (kafka.log.Log) [2017-05-08 08:32:11,678] INFO Truncating log storage-changed-0 to offset 19597. (kafka.log.Log) -- Andrey
