[
https://issues.apache.org/jira/browse/KAFKA-6937?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16491376#comment-16491376
]
Jun Rao commented on KAFKA-6937:
--------------------------------
[~klafferty], thanks for testing this out. Yes, the reason for including the
in-sync replica traffic in the quota is to bound the total replication traffic.
Otherwise, the total replication traffic will be in-sync replication traffic +
replication quota, which can vary as out of sync replicas become in-sync.
> In-sync replica delayed during fetch if replica throttle is exceeded
> --------------------------------------------------------------------
>
> Key: KAFKA-6937
> URL: https://issues.apache.org/jira/browse/KAFKA-6937
> Project: Kafka
> Issue Type: Bug
> Components: core
> Affects Versions: 0.11.0.1, 1.1.0, 1.0.1
> Reporter: Jun Rao
> Assignee: Jun Rao
> Priority: Major
>
> When replication throttling is enabled, in-sync replica's traffic should
> never be throttled. However, in DelayedFetch.tryComplete(), we incorrectly
> delay the completion of an in-sync replica fetch request if replication
> throttling is engaged.
> The impact is that the producer may see increased latency if acks = all. The
> delivery of the message to the consumer may also be delayed.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
