You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@pulsar.apache.org by "Penghui Li (Jira)" <ji...@apache.org> on 2021/01/26 08:19:00 UTC

[jira] [Reopened] (PULSAR-9) Improve the message written count metrics for the topic

     [ https://issues.apache.org/jira/browse/PULSAR-9?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Penghui Li reopened PULSAR-9:
-----------------------------

> Improve the message written count metrics for the topic
> -------------------------------------------------------
>
>                 Key: PULSAR-9
>                 URL: https://issues.apache.org/jira/browse/PULSAR-9
>             Project: Pulsar
>          Issue Type: Improvement
>            Reporter: Penghui Li
>            Priority: Major
>              Labels: Pulsar, gsoc, gsoc2021, mentor
>   Original Estimate: 72h
>  Remaining Estimate: 72h
>
> Currently, Pulsar exposes the message written count metrics though the Prometheus endpoint, and the metrics maintain in the broker, no been persistent. So if the topic ownership changes or restart broker, this will lead to reset the message written count of the topic to 0. This will confused users and not able to get the correct message written count metrics.
> PIP-70 https://github.com/apache/pulsar/wiki/PIP-72%3A-Introduce-Pulsar-Interface-Taxonomy%3A-Audience-and-Stability-Classification[ |https://github.com/apache/pulsar/wiki/PIP-70%3A-Introduce-lightweight-raw-Message-metadata]Introduced a broker level entry metadata which can support message index for a topic(or message offset of a topic), this will provide the ability to calculate the precise message written count for a topic. So we can leverage PIP-70 to improve the message written count metrics for the topic



--
This message was sent by Atlassian Jira
(v8.3.4#803005)