[jira] [Commented] (HBASE-17722) Metrics subsystem stop/start messages add a lot of useless bulk to operational logging

["Andrew Purtell (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/HBASE-17722?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15893581#comment-15893581 ] 

Andrew Purtell commented on HBASE-17722:
----------------------------------------

This should just be an update to log4.properties settings. Just a sec.

> Metrics subsystem stop/start messages add a lot of useless bulk to operational logging
> --------------------------------------------------------------------------------------
>
>                 Key: HBASE-17722
>                 URL: https://issues.apache.org/jira/browse/HBASE-17722
>             Project: HBase
>          Issue Type: Bug
>          Components: metrics
>    Affects Versions: 1.3.0, 1.2.4
>            Reporter: Andrew Purtell
>
> Metrics subsystem stop/start messages add a lot of useless bulk to operational logging. Say you are collecting logs from a fleet of thousands of servers and want to have them around for ~month or longer. It adds up. 
> I think these should at least be at DEBUG level and ideally at TRACE. They don't offer much utility.
> {noformat}
> <time> INFO  [<thread>] impl.MetricsSystemImpl: HBase metrics system started
> <time> INFO  [<thread>] impl.MetricsSystemImpl: Stopping HBase metrics system...
> <time> INFO  [<thread>] impl.MetricsSystemImpl: HBase metrics system stopped.
> <time> INFO  [<thread>] impl.MetricsConfig: loaded properties from hadoop-metrics2-hbase.properties
> <time> INFO  [<thread>] impl.MetricsSystemImpl: Scheduled snapshot period at 10 second(s).
> {noformat}



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)