[
https://issues.apache.org/jira/browse/KAFKA-7130?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16533432#comment-16533432
]
Karsten Schnitter commented on KAFKA-7130:
------------------------------------------
I think the most interesting parts may be the last lines of the dumps:
{code:title=dump-00000000001311940075.log}
baseOffset: 1316626416 lastOffset: 1316626416 baseSequence: -1 lastSequence: -1
producerId: -1 producerEpoch: -1 partitionLeaderEpoch: 51 isTransactional:
false position: 2147481625 CreateTime: 1530618550432 isvalid: true size: 517
magic: 2 compresscodec: LZ4 crc: 103954393
baseOffset: 1316626417 lastOffset: 1316626419 baseSequence: -1 lastSequence: -1
producerId: -1 producerEpoch: -1 partitionLeaderEpoch: 51 isTransactional:
false position: 2147482142 CreateTime: 1530618550435 isvalid: true size: 896
magic: 2 compresscodec: LZ4 crc: 553751416
baseOffset: 1316626420 lastOffset: 1316626420 baseSequence: -1 lastSequence: -1
producerId: -1 producerEpoch: -1 partitionLeaderEpoch: 51 isTransactional:
false position: 2147483038 CreateTime: 1530618550436 isvalid: true size: 600
magic: 2 compresscodec: LZ4 crc: 1152385286
{code}
{code:title=dump-00000000001311940075.index}
offset: 1316626399 position: 2147474054
offset: 1316626407 position: 2147478722
offset: 1316626420 position: 2147483038
{code}
Find both files attached to this issue.
> EOFException after rolling log segment
> --------------------------------------
>
> Key: KAFKA-7130
> URL: https://issues.apache.org/jira/browse/KAFKA-7130
> Project: Kafka
> Issue Type: Bug
> Components: replication
> Affects Versions: 1.1.0
> Reporter: Karsten Schnitter
> Priority: Major
>
> When rolling a log segment one of our Kafka cluster got an immediate read
> error on the same partition. This lead to a flood of log messages containing
> the corresponding stacktraces. Data was still appended to the partition but
> consumers were unable to read from that partition. Reason for the exception
> is unclear.
> {noformat}
> [2018-07-02 23:53:32,732] INFO [Log partition=ingestion-3,
> dir=/var/vcap/store/kafka] Rolled new log segment at offset 971865991 in 1
> ms. (kafka.log.Log)
> [2018-07-02 23:53:32,739] INFO [ProducerStateManager partition=ingestion-3]
> Writing producer snapshot at offset 971865991 (kafka.log.ProducerStateManager)
> [2018-07-02 23:53:32,739] INFO [Log partition=ingestion-3,
> dir=/var/vcap/store/kafka] Rolled new log segment at offset 971865991 in 1
> ms. (kafka.log.Log)
> [2018-07-02 23:53:32,750] ERROR [ReplicaManager broker=1] Error processing
> fetch operation on partition ingestion-3, offset 971865977
> (kafka.server.ReplicaManager)
> Caused by: java.io.EOFException: Failed to read `log header` from file
> channel `sun.nio.ch.FileChannelImpl@2e0e8810`. Expected to read 17 bytes, but
> reached end of file after reading 0 bytes. Started read from position
> 2147483643.
> {noformat}
> We mitigated the issue by stopping the affected node and deleting the
> corresponding directory. Once the partition was recreated for the replica (we
> use replication-factor 2) the other replica experienced the same problem. We
> mitigated likewise.
> To us it is unclear, what caused this issue. Can you help us in finding the
> root cause of this problem?
>
>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
