[
https://issues.apache.org/jira/browse/KAFKA-2419?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14959543#comment-14959543
]
Jay Kreps edited comment on KAFKA-2419 at 10/15/15 8:19 PM:
------------------------------------------------------------
It would be preferable to not need additional threads--we put significant
effort into designing the framework to work without the need for a background
"tick" thread. I agree that this is more a concern on the client than the
server. Is it too complex to just expire sensors as part of other work? E.g.
check for expiry when registering new sensors (after all you don't care about
leaking unless there is growth in the sensor count)
was (Author: jkreps):
It would be preferable to not need additional threads--we put significant
effort into designing it to work without the need for a background "tick"
thread. Is it too complex to just expire sensors as part of other work?
> 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)
