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

Xu Cang commented on HBASE-22762:
---------------------------------

Patch is ready,

output looks like below:

 

1091 2019-07-30 15:01:40,620 INFO [RS:0;xcang-ltm:62046-splits-1564524100198] 
regionserver.SplitRequest(143): Split transaction journal:
1092 STARTED at 1564524100204 (5ms)
1093 PREPARED at 1564524100209 (2ms)
1094 BEFORE_PRE_SPLIT_HOOK at 1564524100211 (0ms)
1095 AFTER_PRE_SPLIT_HOOK at 1564524100211 (2ms)
1096 SET_SPLITTING at 1564524100213 (106ms)
1097 CREATE_SPLIT_DIR at 1564524100319 (30ms)
1098 CLOSED_PARENT_REGION at 1564524100349 (0ms)
1099 OFFLINED_PARENT at 1564524100349 (40ms)
1100 STARTED_REGION_A_CREATION at 1564524100389 (20ms)
1101 STARTED_REGION_B_CREATION at 1564524100409 (14ms)
1102 PONR at 1564524100423 (81ms)
1103 OPENED_REGION_A at 1564524100504 (0ms)
1104 OPENED_REGION_B at 1564524100504 (114ms)
1105 BEFORE_POST_SPLIT_HOOK at 1564524100618 (0ms)
1106 AFTER_POST_SPLIT_HOOK at 1564524100618 (0ms)
1107 COMPLETED at 1564524100618

 

> Print the delta between phases in the split/merge/compact/flush transaction 
> journals
> ------------------------------------------------------------------------------------
>
>                 Key: HBASE-22762
>                 URL: https://issues.apache.org/jira/browse/HBASE-22762
>             Project: HBase
>          Issue Type: Improvement
>          Components: logging
>            Reporter: Andrew Purtell
>            Assignee: Xu Cang
>            Priority: Minor
>
> We print the start timestamp for each phase when logging the 
> split/merge/compact/flush transaction journals and so when debugging an 
> operator must do the math by hand. It would be trivial to also print the 
> delta from the start timestamp of the previous phase and helpful to do so.



--
This message was sent by Atlassian JIRA
(v7.6.14#76016)

Reply via email to