[
https://issues.apache.org/jira/browse/KAFKA-15129?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
hudeqi updated KAFKA-15129:
---------------------------
Description:
In the current kafka code, there are still many module metrics that are
forgotten to be closed when they stop, although some of them have been fixed,
such as kafka-14866 and kafka-14868. et.
These metric leaks may lead to potential OOM risks, and, in the unit tests and
integration tests in the code, there are also a large number of `closes`
without removing the metric, which will also cause CI test instability. By
cleaning up these leaked indicators, these risks can be eliminated, and the
security and stability of the code can be enhanced.
Here I will find all the metrics that are forgotten and closed in the current
version, and submit them according to the subtasks in order to fix them.
was:
In the current kafka code, there are still many module metrics that are
forgotten to be closed when they stop, although some of them have been fixed,
such as kafka-14866 and kafka-14868. et.
Here I will find all the metrics that are forgotten and closed in the current
version, and submit them according to the subtasks in order to fix them.
> Clean up all metrics that were forgotten to be closed
> -----------------------------------------------------
>
> Key: KAFKA-15129
> URL: https://issues.apache.org/jira/browse/KAFKA-15129
> Project: Kafka
> Issue Type: Improvement
> Components: controller, core, log
> Affects Versions: 3.5.0
> Reporter: hudeqi
> Assignee: hudeqi
> Priority: Major
>
> In the current kafka code, there are still many module metrics that are
> forgotten to be closed when they stop, although some of them have been fixed,
> such as kafka-14866 and kafka-14868. et.
> These metric leaks may lead to potential OOM risks, and, in the unit tests
> and integration tests in the code, there are also a large number of `closes`
> without removing the metric, which will also cause CI test instability. By
> cleaning up these leaked indicators, these risks can be eliminated, and the
> security and stability of the code can be enhanced.
> Here I will find all the metrics that are forgotten and closed in the current
> version, and submit them according to the subtasks in order to fix them.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
