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

Hudson commented on HBASE-22225:
--------------------------------

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

(x) {color:red}-1 general checks{color}
-- For more information [see general 
report|https://builds.apache.org/job/HBase%20Nightly/job/master/971//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/master/971//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/master/971//JDK8_Nightly_Build_Report_(Hadoop3)/]


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


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


> Profiler tab on Master/RS UI not working w/o comprehensive message
> ------------------------------------------------------------------
>
>                 Key: HBASE-22225
>                 URL: https://issues.apache.org/jira/browse/HBASE-22225
>             Project: HBase
>          Issue Type: Improvement
>          Components: UI
>    Affects Versions: 1.5.0
>            Reporter: Yu Li
>            Assignee: Andrew Purtell
>            Priority: Minor
>             Fix For: 3.0.0, 1.5.0, 1.4.10, 2.3.0, 2.1.5, 2.2.1, 1.3.5
>
>         Attachments: HBASE-22225-branch-1.patch, HBASE-22225.patch, Screen 
> Shot 2019-04-26 at 4.50.01 PM.jpg
>
>
> As titled, when checking 1.5.0 RC3 binary package, clicking the "Profiler" 
> tab on HMaster/RegionServer web UI, it complains page not found error like 
> below:
> {noformat}
> Problem accessing /prof. Reason:
>     NOT_FOUND
> {noformat}



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

Reply via email to