Hello,

Since we upgraded from Kafka 2.3 to 2.4 we have big amount logs telling:

[2020-05-14 19:34:27,623] ERROR [ReplicaManager broker=1] Error processing
append operation on partition ourtopic-1 (kafka.server.ReplicaManager)
org.apache.kafka.common.InvalidRecordException: Inner record
LegacyRecordBatch(offset=0, Record(magic=1, attributes=0, compression=NONE,
crc=1669125658, CreateTime=1589477470936, key=0 bytes, value=657 bytes))
inside the compressed record batch does not have incremental offsets,
expected offset is 1 in topic partition ourtopic-1.
[2020-05-14 19:34:27,623] ERROR [ReplicaManager broker=1] Error processing
append operation on partition ourtopic-7 (kafka.server.ReplicaManager)
org.apache.kafka.common.InvalidRecordException: Inner record
LegacyRecordBatch(offset=0, Record(magic=1, attributes=0, compression=NONE,
crc=2652410808, CreateTime=1589472087000, key=0 bytes, value=729 bytes))
inside the compressed record batch does not have incremental offsets,
expected offset is 1 in topic partition ourtopic-7.
[2020-05-14 19:34:27,624] ERROR [ReplicaManager broker=1] Error processing
append operation on partition ourtopic-4 (kafka.server.ReplicaManager)
org.apache.kafka.common.InvalidRecordException: Inner record
LegacyRecordBatch(offset=0, Record(magic=1, attributes=0, compression=NONE,
crc=188264511, CreateTime=1589472086000, key=0 bytes, value=730 bytes))
inside the compressed record batch does not have incremental offsets,
expected offset is 1 in topic partition ourtopic-4.

We found the origin in Kafka's source code, but we don't understand the
error message meaning.
Does it mean that very old Kafka clients are connected to our Kafka brokers?
How dangerous is it? What can we do to remove those logs?

Thanks for you help,
Gérald

Reply via email to