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

Hadoop QA commented on HBASE-20806:
-----------------------------------

| (x) *{color:red}-1 overall{color}* |
\\
\\
|| Vote || Subsystem || Runtime || Comment ||
| {color:blue}0{color} | {color:blue} reexec {color} | {color:blue}  0m  
0s{color} | {color:blue} Docker mode activated. {color} |
| {color:red}-1{color} | {color:red} patch {color} | {color:red}  0m  5s{color} 
| {color:red} HBASE-20806 does not apply to branch-2. Rebase required? Wrong 
Branch? See https://yetus.apache.org/documentation/0.7.0/precommit-patchnames 
for help. {color} |
\\
\\
|| Subsystem || Report/Notes ||
| JIRA Issue | HBASE-20806 |
| JIRA Patch URL | 
https://issues.apache.org/jira/secure/attachment/12930844/HBASE-20806.branch-2.001.patch
 |
| Console output | 
https://builds.apache.org/job/PreCommit-HBASE-Build/13548/console |
| Powered by | Apache Yetus 0.7.0   http://yetus.apache.org |


This message was automatically generated.



> Split style journal for flushes and compactions
> -----------------------------------------------
>
>                 Key: HBASE-20806
>                 URL: https://issues.apache.org/jira/browse/HBASE-20806
>             Project: HBase
>          Issue Type: Improvement
>            Reporter: Abhishek Singh Chouhan
>            Assignee: Abhishek Singh Chouhan
>            Priority: Minor
>         Attachments: HBASE-20806.branch-1.001.patch, 
> HBASE-20806.branch-1.002.patch, HBASE-20806.branch-1.003.patch, 
> HBASE-20806.branch-2.001.patch, HBASE-20806.master.001.patch, 
> HBASE-20806.master.002.patch, HBASE-20806.master.003.patch
>
>
> In 1.x we have split transaction journal that gives a clear picture of when 
> various stages of splits took place. We should have a similar thing for 
> flushes and compactions so as to have insights into time spent in various 
> stages, which we can use to identify regressions that might creep up.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Reply via email to