You are viewing a plain text version of this content. The canonical link for it is here.
Posted to jira@kafka.apache.org by "hudeqi (Jira)" <ji...@apache.org> on 2023/04/23 03:18:00 UTC
[jira] [Updated] (KAFKA-14907) Add the traffic metric of the partition dimension in BrokerTopicStats
[ https://issues.apache.org/jira/browse/KAFKA-14907?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
hudeqi updated KAFKA-14907:
---------------------------
Description:
{color:#172b4d}Currently, there are two metrics for measuring the traffic in topic dimensions: MessagesInPerSec, BytesInPerSec, but there are two problems:{color}
{color:#172b4d}1. It is difficult to intuitively reflect the problem of topic partition traffic inclination through these indicators, and it is impossible to clearly see which partition has the largest traffic and the traffic situation of each partition. But the partition dimension can solve this.{color}
{color:#172b4d}2. For the sudden increase in topic traffic (for example, this will lead some followers to out of Isr, which can be avoided by appropriately increasing the number of partitions.), the metrics of the partition dimension can help to provide guidance on whether to expand the partition.{color}
{color:#172b4d}On the whole, I think it is very meaningful to add traffic metrics of partition dimension, especially the issue of traffic skew.{color}
was:
Currently, there are three indicators for measuring topic dimensions: MessagesInPerSec, BytesInPerSec, and BytesOutPerSec, but there are two problems:
1. It is difficult to intuitively reflect the problem of topic partition traffic inclination through these indicators, and it is impossible to clearly see which partition has the largest traffic and the traffic situation of each partition.
2. For the sudden increase in topic traffic, the indicators of the partition dimension can provide guidance on whether to expand the partition and roughly how many partitions to expand.
> Add the traffic metric of the partition dimension in BrokerTopicStats
> ---------------------------------------------------------------------
>
> Key: KAFKA-14907
> URL: https://issues.apache.org/jira/browse/KAFKA-14907
> Project: Kafka
> Issue Type: Improvement
> Components: core
> Affects Versions: 3.3.2
> Reporter: hudeqi
> Assignee: hudeqi
> Priority: Major
>
> {color:#172b4d}Currently, there are two metrics for measuring the traffic in topic dimensions: MessagesInPerSec, BytesInPerSec, but there are two problems:{color}
> {color:#172b4d}1. It is difficult to intuitively reflect the problem of topic partition traffic inclination through these indicators, and it is impossible to clearly see which partition has the largest traffic and the traffic situation of each partition. But the partition dimension can solve this.{color}
> {color:#172b4d}2. For the sudden increase in topic traffic (for example, this will lead some followers to out of Isr, which can be avoided by appropriately increasing the number of partitions.), the metrics of the partition dimension can help to provide guidance on whether to expand the partition.{color}
> {color:#172b4d}On the whole, I think it is very meaningful to add traffic metrics of partition dimension, especially the issue of traffic skew.{color}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)