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

Posted to dev@bookkeeper.apache.org by "Ankur Garg (JIRA)" <ji...@apache.org> on 2015/07/31 20:08:04 UTC

[jira] [Assigned] (BOOKKEEPER-812) StatsLogger doesn't cache counters/stats-loggers

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

Ankur Garg reassigned BOOKKEEPER-812:
-------------------------------------

    Assignee: Ankur Garg

> StatsLogger doesn't cache counters/stats-loggers
> ------------------------------------------------
>
>                 Key: BOOKKEEPER-812
>                 URL: https://issues.apache.org/jira/browse/BOOKKEEPER-812
>             Project: Bookkeeper
>          Issue Type: Improvement
>            Reporter: Charles X
>            Assignee: Ankur Garg
>
> Currently the stats providers implementation doesn't provide caching ability for counters/stats loggers for different metrics. if the underlying stats library (e.g. code hale, ostrich) doesn't provide that, the client would end up creating different instances for same metric name, which would introduce bad gc behavior.
> it would be better that bookkeeper-stats-provider could address this in high level, rather than ask individual stats provider implementing similar caching behavior.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)