[
https://issues.apache.org/jira/browse/KAFKA-2477?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14731210#comment-14731210
]
Jun Rao commented on KAFKA-2477:
--------------------------------
Thanks. Then the log looks normal. The only thing that I can recommend now is
to try reproducing the issue locally and apply the trace level logging.
Also, since you are using snappy, you may want to apply the fixes in 0.8.2.2
(https://people.apache.org/~junrao/kafka-0.8.2.2-candidate1/RELEASE_NOTES.html)
once it's out. They may not be related to the issue that you are seeing here
though.
> 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)
