[
https://issues.apache.org/jira/browse/HBASE-1706?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andrew Purtell updated HBASE-1706:
----------------------------------
Attachment: HBASE-1706.patch
Patch addresses the symptom and gets the UI working again.
> META row with missing HRI breaks UI
> -----------------------------------
>
> Key: HBASE-1706
> URL: https://issues.apache.org/jira/browse/HBASE-1706
> Project: Hadoop HBase
> Issue Type: Bug
> Reporter: Andrew Purtell
> Priority: Critical
> Fix For: 0.20.0
>
> Attachments: HBASE-1706.patch
>
>
> Seeing this in the master log:
> 2009-07-26 06:01:55,373 WARN org.apache.hadoop.hbase.master.BaseScanner:
> Found 1 rows with empty HRegionInfo while scanning meta region .META.,,1
> 2009-07-26 06:01:55,373 WARN org.apache.hadoop.hbase.master.HMaster: Removed
> region: content,9e1f3dbffe50886f56d67044ca7177e,1248262776854 from meta
> region: .META.,,1 because HRegionInfo was empty
> Seeing this on the master UI (http://test:60010/master.jsp):
> HTTP ERROR: 500
> INTERNAL_SERVER_ERROR
> RequestURI=/master.jsp
> Caused by:
> java.lang.NullPointerException
> at org.apache.hadoop.hbase.util.Writables.getWritable(Writables.java:74)
> at
> org.apache.hadoop.hbase.util.Writables.getHRegionInfo(Writables.java:118)
> at
> org.apache.hadoop.hbase.client.HConnectionManager$TableServers$1.processRow(HConnectionManager.java:356)
> at
> org.apache.hadoop.hbase.client.MetaScanner.metaScan(MetaScanner.java:63)
> at
> org.apache.hadoop.hbase.client.MetaScanner.metaScan(MetaScanner.java:28)
> at
> org.apache.hadoop.hbase.client.HConnectionManager$TableServers.listTables(HConnectionManager.java:369)
> at
> org.apache.hadoop.hbase.client.HBaseAdmin.listTables(HBaseAdmin.java:127)
> at
> org.apache.hadoop.hbase.generated.master.master_jsp._jspService(master_jsp.java:125)
> at org.apache.jasper.runtime.HttpJspBase.service(HttpJspBase.java:97)
> at javax.servlet.http.HttpServlet.service(HttpServlet.java:820)
> at
> org.mortbay.jetty.servlet.ServletHolder.handle(ServletHolder.java:502)
> at
> org.mortbay.jetty.servlet.ServletHandler.handle(ServletHandler.java:363)
> at
> org.mortbay.jetty.security.SecurityHandler.handle(SecurityHandler.java:216)
> at
> org.mortbay.jetty.servlet.SessionHandler.handle(SessionHandler.java:181)
> at
> org.mortbay.jetty.handler.ContextHandler.handle(ContextHandler.java:766)
> at org.mortbay.jetty.webapp.WebAppContext.handle(WebAppContext.java:417)
> at
> org.mortbay.jetty.handler.ContextHandlerCollection.handle(ContextHandlerCollection.java:230)
> at
> org.mortbay.jetty.handler.HandlerWrapper.handle(HandlerWrapper.java:152)
> at org.mortbay.jetty.Server.handle(Server.java:324)
> at
> org.mortbay.jetty.HttpConnection.handleRequest(HttpConnection.java:534)
> at
> org.mortbay.jetty.HttpConnection$RequestHandler.headerComplete(HttpConnection.java:864)
> at org.mortbay.jetty.HttpParser.parseNext(HttpParser.java:533)
> at org.mortbay.jetty.HttpParser.parseAvailable(HttpParser.java:207)
> at org.mortbay.jetty.HttpConnection.handle(HttpConnection.java:403)
> at
> org.mortbay.io.nio.SelectChannelEndPoint.run(SelectChannelEndPoint.java:409)
> at
> org.mortbay.thread.QueuedThreadPool$PoolThread.run(QueuedThreadPool.java:522)
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
