hbase-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Andrew Purtell (JIRA)" <j...@apache.org>
Subject [jira] [Created] (HBASE-17722) Metrics subsystem stop/start messages add a lot of useless bulk to operational logging
Date Fri, 03 Mar 2017 01:57:45 GMT
Andrew Purtell created HBASE-17722:
--------------------------------------

             Summary: 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.2.4, 1.3.0
            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)

Mime
View raw message