[
https://issues.apache.org/jira/browse/HBASE-19450?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16975598#comment-16975598
]
Sean Busbey commented on HBASE-19450:
-------------------------------------
> Maybe a better way is that, for the trace log(or debug log? I never enable
> trace on cluster actually...),
logging these without the "no more often then X" guard shouldn't happen at
DEBUG IMHO. I have seen plenty of times that we enable debug on all classes for
a given server and these messages will overwhelm the logs without adding much
value for such a broad action. It's possible there's a time you'd still want to
see how the average window is moving more often for something like the split
manager timeout manager, in which case enabling TRACE on *just* this class is
what I'd do.
> Add log about average execution time for ScheduledChore
> -------------------------------------------------------
>
> Key: HBASE-19450
> URL: https://issues.apache.org/jira/browse/HBASE-19450
> Project: HBase
> Issue Type: Improvement
> Components: Operability
> Reporter: Reid Chan
> Assignee: Reid Chan
> Priority: Minor
> Fix For: 3.0.0, 2.3.0, 2.1.8, 2.2.3
>
> Attachments: HBASE-19450.addendum1.0.patch,
> HBASE-19450.master.001.patch, HBASE-19450.master.002.patch,
> HBASE-19450.master.003.patch, HBASE-19450.master.004.patch
>
>
> So far, there is no information about the exact execution time for a chore,
> we can provide log information about it. It also brings other benefits, like
> discovering inefficient chores which show rooms for improvement.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
