You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@kafka.apache.org by "Jun Rao (JIRA)" <ji...@apache.org> on 2015/09/01 03:40:46 UTC

[jira] [Commented] (KAFKA-2477) Replicas spuriously deleting all segments in partition

    [ https://issues.apache.org/jira/browse/KAFKA-2477?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14724559#comment-14724559 ] 

Jun Rao commented on KAFKA-2477:
--------------------------------

Interesting, so there is nothing in broker 0's log about truncating the log for partition [log.event,3]? 

It seems that this is reproducible. Would it be possible for you to enable TRACE level logging for class kafka.log.Log on every broker. This will log the new log end offset after each message append. When this issue happens again, we can verify if it is indeed that the follower uses a fetch offset that's larger than the leader's log end offset.

> Replicas spuriously deleting all segments in partition
> ------------------------------------------------------
>
>                 Key: KAFKA-2477
>                 URL: https://issues.apache.org/jira/browse/KAFKA-2477
>             Project: Kafka
>          Issue Type: Bug
>    Affects Versions: 0.8.2.1
>            Reporter: Håkon Hitland
>         Attachments: kafka_log.txt
>
>
> We're seeing some strange behaviour in brokers: a replica will sometimes schedule all segments in a partition for deletion, and then immediately start replicating them back, triggering our check for under-replicating topics.
> This happens on average a couple of times a week, for different brokers and topics.
> We have per-topic retention.ms and retention.bytes configuration, the topics where we've seen this happen are hitting the size limit.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)