[
https://issues.apache.org/jira/browse/HBASE-25980?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17360683#comment-17360683
]
Zhuoyue Huang commented on HBASE-25980:
---------------------------------------
I reproduced this bug and saw the same result as the description. Code below
was called in table.js and the rit region make this call throw a
NotAllMetaRegionsOnlineException.
{code:java}
MetaTableLocator.waitMetaRegionLocation(master.getZooKeeper(), j, 1)
{code}
IMHO , as the meta replica is in rit, we should simply ignore this Exception
and show the default value of meta region replica on UI.
Has tried to fix this, the screenshot in attachments show what it look like
after fixed
> Master table.jsp pointed at meta throws 500 when no all replicas are online
> ---------------------------------------------------------------------------
>
> Key: HBASE-25980
> URL: https://issues.apache.org/jira/browse/HBASE-25980
> Project: HBase
> Issue Type: Bug
> Components: master, meta replicas, UI
> Affects Versions: 2.3.5
> Reporter: Nick Dimiduk
> Assignee: Zhuoyue Huang
> Priority: Major
> Attachments: base_stats.png, compaction.png, localities.png,
> meta_replica_rit.png
>
>
> With a replica in a transition state, the UI renders,
> {noformat}
> HTTP ERROR 500
> Problem accessing /table.jsp. Reason:
> Server Error
> Caused by:
> org.apache.hadoop.hbase.NotAllMetaRegionsOnlineException: Timed out; 1ms
> at
> org.apache.hadoop.hbase.zookeeper.MetaTableLocator.waitMetaRegionLocation(MetaTableLocator.java:190)
> at
> org.apache.hadoop.hbase.generated.master.table_jsp._jspService(table_jsp.java:264)
> at org.apache.jasper.runtime.HttpJspBase.service(HttpJspBase.java:111)
> at javax.servlet.http.HttpServlet.service(HttpServlet.java:790)
> {noformat}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
