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

Hudson commented on HBASE-28315:
--------------------------------

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

(/) {color:green}+1 general checks{color}
-- For more information [see general 
report|https://ci-hbase.apache.org/job/HBase%20Nightly/job/branch-3/134/General_20Nightly_20Build_20Report/]




(/) {color:green}+1 jdk8 hadoop3 checks{color}
-- For more information [see jdk8 (hadoop3) 
report|https://ci-hbase.apache.org/job/HBase%20Nightly/job/branch-3/134/JDK8_20Nightly_20Build_20Report_20_28Hadoop3_29/]


(/) {color:green}+1 jdk11 hadoop3 checks{color}
-- For more information [see jdk11 
report|https://ci-hbase.apache.org/job/HBase%20Nightly/job/branch-3/134/JDK11_20Nightly_20Build_20Report_20_28Hadoop3_29/]


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


(x) {color:red}-1 client integration test{color}
--Failed when running client tests on top of Hadoop 3. [see log for 
details|https://ci-hbase.apache.org/job/HBase%20Nightly/job/branch-3/134//artifact/output-integration/hadoop-3.log].
 (note that this means we didn't check the Hadoop 3 shaded client)


> Remove noisy WARN from trying to construct MetricsServlet
> ---------------------------------------------------------
>
>                 Key: HBASE-28315
>                 URL: https://issues.apache.org/jira/browse/HBASE-28315
>             Project: HBase
>          Issue Type: Bug
>    Affects Versions: 3.0.0-beta-1
>            Reporter: Bryan Beaudreault
>            Assignee: Bryan Beaudreault
>            Priority: Major
>             Fix For: 2.6.0, 3.0.0-beta-2
>
>
> MetricsServlet is deprecated since hadoop 2.8 and removed in hadoop3. In 
> HBASE-20904 the servlet initialization was refactored, and we now have a 
> noisy WARN (with stacktrace) when MetricsServlet does not exist. This should 
> be common, since hadoop3 is the modern version to run on (hadoop2 almost 
> EOL). We shouldn't warn.
> Fix the code to not produce a warn when MetricsServlet is not available.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

Reply via email to