[
https://issues.apache.org/jira/browse/HBASE-22751?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16895720#comment-16895720
]
Hudson commented on HBASE-22751:
--------------------------------
Results for branch master
[build #1288 on
builds.a.o|https://builds.apache.org/job/HBase%20Nightly/job/master/1288/]: (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/master/1288//General_Nightly_Build_Report/]
(x) {color:red}-1 jdk8 hadoop2 checks{color}
-- For more information [see jdk8 (hadoop2)
report|https://builds.apache.org/job/HBase%20Nightly/job/master/1288//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/1288//JDK8_Nightly_Build_Report_(Hadoop3)/]
(/) {color:green}+1 source release artifact{color}
-- See build output for details.
(/) {color:green}+1 client integration test{color}
> table.jsp fails if ugly regions in table
> ----------------------------------------
>
> Key: HBASE-22751
> URL: https://issues.apache.org/jira/browse/HBASE-22751
> Project: HBase
> Issue Type: Bug
> Components: UI
> Reporter: stack
> Assignee: stack
> Priority: Major
> Fix For: 3.0.0, 2.3.0, 2.0.6, 2.2.1, 2.1.6
>
> Attachments: HBASE-22751.master.001.patch,
> HBASE-22751.master.001.patch
>
>
> I'm playing w/ messing up hbase:meta as part of hbck2 messings. Noticed that
> a bad server or an unknown region makes it so the table.jsp fails.
> I noticed that Admin trying to get the compaction stats for the table will
> get stuck trying to contact an unknown region and that when it does complete
> eventually (tens of minutes...), it will spew an exception in the compaction
> state location.
> The listing of servers has an issue where if unknown server, then we'll try
> to use a null address which does another spew of jsp complaint instead of
> just logging an unknown....
> I tried messing around with Admin trying to set its Operation Timeout... but
> Operation Timeout is not really settable unless you get a new Configuration
> for a new Connection -- which is madness -- so instead just used the new
> AsyncAdminBuilder where I can set operation timeout....
> It times out too quick but thats another issue.... the UI at least draws with
> a messy hbase;meta.
--
This message was sent by Atlassian JIRA
(v7.6.14#76016)
