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

Michael Stack commented on HBASE-19450:
---------------------------------------

Built branch-2 and ran in standalone mode.... Logs are filled with this sort of 
stuff....
{code}
 2019-11-15 14:49:59,118 INFO  [regionserver/localhost:16020.Chore.1] 
hbase.ScheduledChore: CompactionChecker average execution time: 7532.00 ns.
 2019-11-15 14:49:59,118 INFO  [regionserver/localhost:16020.Chore.1] 
hbase.ScheduledChore: MemstoreFlusherChore average execution time: 12188.60 ns.
 2019-11-15 14:49:59,141 INFO  
[master/localhost:16000.splitLogManager..Chore.1] hbase.ScheduledChore: 
SplitLogManager Timeout Monitor average execution time: 3955.20 ns.
 2019-11-15 14:50:00,141 INFO  
[master/localhost:16000.splitLogManager..Chore.1] hbase.ScheduledChore: 
SplitLogManager Timeout Monitor average execution time: 3811.60 ns.
 2019-11-15 14:50:01,141 INFO  
[master/localhost:16000.splitLogManager..Chore.1] hbase.ScheduledChore: 
SplitLogManager Timeout Monitor average execution time: 3904.20 ns.
 2019-11-15 14:50:02,140 INFO  
[master/localhost:16000.splitLogManager..Chore.1] hbase.ScheduledChore: 
SplitLogManager Timeout Monitor average execution time: 3878.60 ns.
 2019-11-15 14:50:03,141 INFO  
[master/localhost:16000.splitLogManager..Chore.1] hbase.ScheduledChore: 
SplitLogManager Timeout Monitor average execution time: 3907.80 ns.
 2019-11-15 14:50:04,144 INFO  
[master/localhost:16000.splitLogManager..Chore.1] hbase.ScheduledChore: 
SplitLogManager Timeout Monitor average execution time: 3873.00 ns.
 2019-11-15 14:50:05,141 INFO  
[master/localhost:16000.splitLogManager..Chore.1] hbase.ScheduledChore: 
SplitLogManager Timeout Monitor average execution time: 4064.80 ns.
 2019-11-15 14:50:06,141 INFO  
[master/localhost:16000.splitLogManager..Chore.1] hbase.ScheduledChore: 
SplitLogManager Timeout Monitor average execution time: 3993.20 ns.
 2019-11-15 14:50:07,139 INFO  
[master/localhost:16000.splitLogManager..Chore.1] hbase.ScheduledChore: 
SplitLogManager Timeout Monitor average execution time: 4072.60 ns.
 2019-11-15 14:50:08,144 INFO  
[master/localhost:16000.splitLogManager..Chore.1] hbase.ScheduledChore: 
SplitLogManager Timeout Monitor average execution time: 4049.60 ns.
 2019-11-15 14:50:09,142 INFO  
[master/localhost:16000.splitLogManager..Chore.1] hbase.ScheduledChore: 
SplitLogManager Timeout Monitor average execution time: 4134.60 ns.
 2019-11-15 14:50:09,363 INFO  [regionserver/localhost:16020.Chore.1] 
hbase.ScheduledChore: MemstoreFlusherChore average execution time: 11454.40 ns.
 2019-11-15 14:50:09,363 INFO  [regionserver/localhost:16020.Chore.1] 
hbase.ScheduledChore: CompactionChecker average execution time: 7346.60 ns.
 2019-11-15 14:50:10,143 INFO  
[master/localhost:16000.splitLogManager..Chore.1] hbase.ScheduledChore: 
SplitLogManager Timeout Monitor average execution time: 4124.60 ns.
 2019-11-15 14:50:11,141 INFO  
[master/localhost:16000.splitLogManager..Chore.1] hbase.ScheduledChore: 
SplitLogManager Timeout Monitor average execution time: 4222.20 ns.
 2019-11-15 14:50:12,144 INFO  
[master/localhost:16000.splitLogManager..Chore.1] hbase.ScheduledChore: 
SplitLogManager Timeout Monitor average execution time: 4233.20 ns.
 2019-11-15 14:50:13,142 INFO  
[master/localhost:16000.splitLogManager..Chore.1] hbase.ScheduledChore: 
SplitLogManager Timeout Monitor average execution time: 4067.40 ns.
 2019-11-15 14:50:14,143 INFO  
[master/localhost:16000.splitLogManager..Chore.1] hbase.ScheduledChore: 
SplitLogManager Timeout Monitor average execution time: 3896.80 ns.
 2019-11-15 14:50:15,140 INFO  
[master/localhost:16000.splitLogManager..Chore.1] hbase.ScheduledChore: 
SplitLogManager Timeout Monitor average execution time: 3941.80 ns.
 2019-11-15 14:50:16,143 INFO  
[master/localhost:16000.splitLogManager..Chore.1] hbase.ScheduledChore: 
SplitLogManager Timeout Monitor average execution time: 3902.60 ns.
 2019-11-15 14:50:17,144 INFO  
[master/localhost:16000.splitLogManager..Chore.1] hbase.ScheduledChore: 
SplitLogManager Timeout Monitor average execution time: 3929.40 ns.
 2019-11-15 14:50:18,143 INFO  
[master/localhost:16000.splitLogManager..Chore.1] hbase.ScheduledChore: 
SplitLogManager Timeout Monitor average execution time: 3901.80 ns.
 2019-11-15 14:50:19,139 INFO  
[master/localhost:16000.splitLogManager..Chore.1] hbase.ScheduledChore: 
SplitLogManager Timeout Monitor average execution time: 4147.40 ns.
 2019-11-15 14:50:19,602 INFO  [regionserver/localhost:16020.Chore.1] 
hbase.ScheduledChore: MemstoreFlusherChore average execution time: 13649.20 ns.
 2019-11-15 14:50:19,602 INFO  [regionserver/localhost:16020.Chore.1] 
hbase.ScheduledChore: CompactionChecker average execution time: 7153.40 ns.
 2019-11-15 14:50:20,144 INFO  
[master/localhost:16000.splitLogManager..Chore.1] hbase.ScheduledChore: 
SplitLogManager Timeout Monitor average execution time: 3959.00 ns.
 2019-11-15 14:50:21,139 INFO  
[master/localhost:16000.splitLogManager..Chore.1] hbase.ScheduledChore: 
SplitLogManager Timeout Monitor average execution time: 3614.00 ns.
 2019-11-15 14:50:22,141 INFO  
[master/localhost:16000.splitLogManager..Chore.1] hbase.ScheduledChore: 
SplitLogManager Timeout Monitor average execution time: 3338.40 ns.
 2019-11-15 14:50:23,143 INFO  
[master/localhost:16000.splitLogManager..Chore.1] hbase.ScheduledChore: 
SplitLogManager Timeout Monitor average execution time: 3110.40 ns.
 2019-11-15 14:50:24,141 INFO  
[master/localhost:16000.splitLogManager..Chore.1] hbase.ScheduledChore: 
SplitLogManager Timeout Monitor average execution time: 2901.60 ns.
 2019-11-15 14:50:25,143 INFO  
[master/localhost:16000.splitLogManager..Chore.1] hbase.ScheduledChore: 
SplitLogManager Timeout Monitor average execution time: 2735.80 ns.
 2019-11-15 14:50:26,143 INFO  
[master/localhost:16000.splitLogManager..Chore.1] hbase.ScheduledChore: 
SplitLogManager Timeout Monitor average execution time: 2844.40 ns.
 2019-11-15 14:50:27,142 INFO  
[master/localhost:16000.splitLogManager..Chore.1] hbase.ScheduledChore: 
SplitLogManager Timeout Monitor average execution time: 2888.80 ns.
 2019-11-15 14:50:28,141 INFO  
[master/localhost:16000.splitLogManager..Chore.1] hbase.ScheduledChore: 
SplitLogManager Timeout Monitor average execution time: 3311.60 ns.
 2019-11-15 14:50:28,874 INFO  [regionserver/localhost:16020.Chore.1] 
hbase.ScheduledChore: CompactionChecker average execution time: 7081.80 ns.
 2019-11-15 14:50:28,874 INFO  [regionserver/localhost:16020.Chore.1] 
hbase.ScheduledChore: MemstoreFlusherChore average execution time: 13628.60 ns.
{code}


> 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.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)

Reply via email to