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

Hudson commented on HBASE-22828:
--------------------------------

Results for branch branch-2.2
        [build #514 on 
builds.a.o|https://builds.apache.org/job/HBase%20Nightly/job/branch-2.2/514/]: 
(x) *{color:red}-1 overall{color}*
----
details (if available):

(/) {color:green}+1 general checks{color}
-- For more information [see general 
report|https://builds.apache.org/job/HBase%20Nightly/job/branch-2.2/514//General_Nightly_Build_Report/]




(/) {color:green}+1 jdk8 hadoop2 checks{color}
-- For more information [see jdk8 (hadoop2) 
report|https://builds.apache.org/job/HBase%20Nightly/job/branch-2.2/514//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/514//JDK8_Nightly_Build_Report_(Hadoop3)/]


(/) {color:green}+1 source release artifact{color}
-- See build output for details.


(/) {color:green}+1 client integration test{color}


> Log a region close journal
> --------------------------
>
>                 Key: HBASE-22828
>                 URL: https://issues.apache.org/jira/browse/HBASE-22828
>             Project: HBase
>          Issue Type: Improvement
>            Reporter: Andrew Purtell
>            Assignee: Andrew Purtell
>            Priority: Minor
>             Fix For: 3.0.0, 1.5.0, 2.2.1, 2.1.6, 1.3.6, 1.4.11
>
>         Attachments: HBASE-22828-branch-1.patch, HBASE-22828.patch
>
>
> We already track region close activity with a MonitoredTask. Enable the 
> status journal and dump it at DEBUG log level so if for some reasons region 
> closes are taking a long time we have a timestamped journal of the activity 
> and how long each step took. 



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

Reply via email to