[
https://issues.apache.org/jira/browse/KAFKA-2419?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14875986#comment-14875986
]
Joel Koshy commented on KAFKA-2419:
-----------------------------------
However, we should think through the effect of doing this. i.e., consider
topic-level metrics that are only updated when there is active traffic to/from
a topic. So for e.g., if there are topics with intermittent pushes of data
(e.g., from hadoop to Kafka) you may delete those metrics which would
(depending on what monitoring framework you use) typically manifest in gaps -
so it will be hard to tell if it is an issue with the monitoring framework or
whether that topic just got deleted - likewise for quotas. That won't occur
with explicit deletion. So maybe we should go with (2) or (3) unless the
caveats of (1) (which is the simplest approach) are not a major concern.
> Allow certain Sensors to be garbage collected after inactivity
> --------------------------------------------------------------
>
> Key: KAFKA-2419
> URL: https://issues.apache.org/jira/browse/KAFKA-2419
> Project: Kafka
> Issue Type: New Feature
> Affects Versions: 0.9.0.0
> Reporter: Aditya Auradkar
> Assignee: Aditya Auradkar
> Priority: Blocker
> Labels: quotas
> Fix For: 0.9.0.0
>
>
> Currently, metrics cannot be removed once registered.
> Implement a feature to remove certain sensors after a certain period of
> inactivity (perhaps configurable).
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
