[
https://issues.apache.org/jira/browse/KAFKA-4888?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15926322#comment-15926322
]
Jun Rao commented on KAFKA-4888:
--------------------------------
[~eduardo.s.neto] and [~chengc], is the issue persistent, i.e., if you consume
from the same offset again, do you see the same CRC error? Also, it would be
useful to run bin/kafka-run-class.sh kafka.tools.DumpLogSegments on the segment
of the affected offset and see if the message is actually corrupted on disk (in
all replicas).
> offset 449883 is invalid, cause: Record is corrupt (stored crc = 2171407101,
> computed crc = 1371274824)
> -------------------------------------------------------------------------------------------------------
>
> Key: KAFKA-4888
> URL: https://issues.apache.org/jira/browse/KAFKA-4888
> Project: Kafka
> Issue Type: Bug
> Components: consumer
> Affects Versions: 0.10.1.1
> Environment: Release version:
> LSB Version:
> :base-4.0-amd64:base-4.0-noarch:core-4.0-amd64:core-4.0-noarch:graphics-4.0-amd64:graphics-4.0-noarch:printing-4.0-amd64:printing-4.0-noarch
> Distributor ID: RedHatEnterpriseServer
> Description: Red Hat Enterprise Linux Server release 6.5 (Santiago)
> Release: 6.5
> Codename: Santiago
> Memory SO:
> Mem: 15.577G total, 15.416G used, 164.508M free, 49.895M buffers
> Filesystem
> Filesystem Size Used Avail Use% Mounted on
> /dev/mapper/appvg-lv_opt
> 30G 1018M 28G 20% /opt/ngin
> Reporter: Eduardo da Silva Neto
> Attachments: issue_kafka
>
> Original Estimate: 168h
> Remaining Estimate: 168h
>
> We created five kafka consumers that consume with one message at a time
> max.poll.records = 1. After two days of intensive processing with the kafka
> server file system with about 50% used the corrupted registry error occurred.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
