[
https://issues.apache.org/jira/browse/KAFKA-1461?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14357668#comment-14357668
]
Jun Rao commented on KAFKA-1461:
--------------------------------
[~sriharsha] and [~guozhang], thinking about this a bit more. There are really
two types of states that we need to manage in AbstractFetcherThread. The first
one is the connection state, i.e., if a connection breaks, we want to backoff
the reconnection. The second one is the partition state, i.e., if the partition
hits an exception, we want to backoff that particular partition a bit.
The first one is what [~sriharsha]'s current RB is addressing. How about let's
complete this first since it affects the performance of the unit tests? Once
that's committed, we can address the second one, which is in [~sriharsha]'s
initial patch.
> Replica fetcher thread does not implement any back-off behavior
> ---------------------------------------------------------------
>
> Key: KAFKA-1461
> URL: https://issues.apache.org/jira/browse/KAFKA-1461
> Project: Kafka
> Issue Type: Improvement
> Components: replication
> Affects Versions: 0.8.1.1
> Reporter: Sam Meder
> Assignee: Sriharsha Chintalapani
> Labels: newbie++
> Fix For: 0.8.3
>
> Attachments: KAFKA-1461.patch, KAFKA-1461.patch,
> KAFKA-1461_2015-03-11_10:41:26.patch
>
>
> The current replica fetcher thread will retry in a tight loop if any error
> occurs during the fetch call. For example, we've seen cases where the fetch
> continuously throws a connection refused exception leading to several replica
> fetcher threads that spin in a pretty tight loop.
> To a much lesser degree this is also an issue in the consumer fetcher thread,
> although the fact that erroring partitions are removed so a leader can be
> re-discovered helps some.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
