[
https://issues.apache.org/jira/browse/KUDU-2279?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Todd Lipcon resolved KUDU-2279.
-------------------------------
Resolution: Fixed
Fix Version/s: 1.7.0
> Enable metrics logging by default
> ---------------------------------
>
> Key: KUDU-2279
> URL: https://issues.apache.org/jira/browse/KUDU-2279
> Project: Kudu
> Issue Type: New Feature
> Components: ops-tooling
> Affects Versions: 1.7.0
> Reporter: Todd Lipcon
> Assignee: Todd Lipcon
> Priority: Major
> Fix For: 1.7.0
>
>
> In a lot of cases, the granular metrics that we collect can be very useful to
> understand performance problems. Our internal metrics tend to be much more
> granular than what is supported by common metrics aggregation systems, so
> having the local metrics log is useful even in the context of a managed
> deployment. So, I'd like to move towards enabling metrics logging by default.
> Currently, however, the metrics log can be quite verbose, since it's
> equivalent to dumping all of the /metricsjson endpoint on a periodic basis.
> Even though we gzip it, we burn a lot of CPU serializing a huge blob (eg
> /metricsjson is 87MB on a tserver in one of our test clusters). Additionally,
> we don't currently have the ability to delete old metrics logs automatically,
> so we'd be in danger of filling up the log dir.
> This JIRA tracks various bits of work on the way to enabling metrics logging
> by default.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
