You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@hbase.apache.org by "Nick Dimiduk (Jira)" <ji...@apache.org> on 2020/05/13 22:31:00 UTC
[jira] [Created] (HBASE-24367) ScheduledChore log elapsed timespan
in a human-friendly format
Nick Dimiduk created HBASE-24367:
------------------------------------
Summary: ScheduledChore log elapsed timespan in a human-friendly format
Key: HBASE-24367
URL: https://issues.apache.org/jira/browse/HBASE-24367
Project: HBase
Issue Type: Task
Components: master, regionserver
Affects Versions: 2.3.0
Reporter: Nick Dimiduk
I noticed this in a log line,
{noformat}
2020-04-23 18:31:14,183 INFO org.apache.hadoop.hbase.ScheduledChore: host-a.example.com,16000,1587577999888-ClusterStatusChore average execution time: 68488258 ns.
{noformat}
I'm not sure if there's a case when elapsed time in nanoseconds is meaningful for these background chores, but we could do a little work before printing the number and time unit to truncate precision down to something a little more intuitive for operators. This number purports to be an average, so a high level of precision isn't necessarily meaningful.
Separately, or while we're here, if we think an operator really cares about the performance of this chore, we should print a histogram of elapsed times, rather than an opaque average.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)