[
https://issues.apache.org/jira/browse/KAFKA-2477?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14741275#comment-14741275
]
ASF GitHub Bot commented on KAFKA-2477:
---------------------------------------
GitHub user becketqin reopened a pull request:
https://github.com/apache/kafka/pull/204
KAFKA-2477: Fix a race condition between log append and fetch that causes
OffsetOutOfRangeException.
Tried two fixes. I prefer the second approach because it saves an
additional offset search.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/becketqin/kafka KAFKA-2477
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/kafka/pull/204.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #204
----
commit e7610fb69a4007ae661a768635e930355c8caa76
Author: Jiangjie Qin <becket....@gmail.com>
Date: 2015-09-11T02:17:12Z
KAFKA-2477: Fix a race condition between log append and fetch that causes
OffsetOutOfRangeException
commit 45364d76e756fc6075924b3a07651b7fbbcc391a
Author: Jiangjie Qin <becket....@gmail.com>
Date: 2015-09-11T03:06:35Z
A second fix that avoids an addition offset search
----
> 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
> Assignee: Jiangjie Qin
> Attachments: kafka_log.txt, kafka_log_trace.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)
