You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@kafka.apache.org by "Vahid Hashemian (Jira)" <ji...@apache.org> on 2020/03/17 17:23:00 UTC
[jira] [Created] (KAFKA-9731) Increased fetch request rate with
leader selector due to HW propagation
Vahid Hashemian created KAFKA-9731:
--------------------------------------
Summary: Increased fetch request rate with leader selector due to HW propagation
Key: KAFKA-9731
URL: https://issues.apache.org/jira/browse/KAFKA-9731
Project: Kafka
Issue Type: Improvement
Components: core
Affects Versions: 2.4.1, 2.4.0
Reporter: Vahid Hashemian
Attachments: image-2020-03-17-10-19-08-987.png
KIP-392 adds high watermark propagation to followers as a means to better sync up followers HW with leader. The issue we have noticed after trying out 2.4.0 and 2.4.1 is a spike in fetch request rate in the default selector case (leader), that does not really require this high watermark propagation:
!image-2020-03-17-10-19-08-987.png|width=811,height=354!
This spike causes an increase in resource allocation (CPU) on the brokers.
An easy solution would be to disable this propagation (at least) for the default leader selector case to improve the backward compatibility.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)