[
https://issues.apache.org/jira/browse/HBASE-24367?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17129868#comment-17129868
]
Hudson commented on HBASE-24367:
--------------------------------
Results for branch branch-2.2
[build #889 on
builds.a.o|https://builds.apache.org/job/HBase%20Nightly/job/branch-2.2/889/]:
(x) *{color:red}-1 overall{color}*
----
details (if available):
(x) {color:red}-1 general checks{color}
-- For more information [see general
report|https://builds.apache.org/job/HBase%20Nightly/job/branch-2.2/889//General_Nightly_Build_Report/]
(x) {color:red}-1 jdk8 hadoop2 checks{color}
-- For more information [see jdk8 (hadoop2)
report|https://builds.apache.org/job/HBase%20Nightly/job/branch-2.2/889//JDK8_Nightly_Build_Report_(Hadoop2)/]
(x) {color:red}-1 jdk8 hadoop3 checks{color}
-- For more information [see jdk8 (hadoop3)
report|https://builds.apache.org/job/HBase%20Nightly/job/branch-2.2/889//JDK8_Nightly_Build_Report_(Hadoop3)/]
(/) {color:green}+1 source release artifact{color}
-- See build output for details.
(/) {color:green}+1 client integration test{color}
> 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
> Assignee: Andrew Kyle Purtell
> Priority: Minor
> Fix For: 3.0.0-alpha-1, 2.3.0, 2.2.6
>
>
> 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)
