You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@hbase.apache.org by "stack (JIRA)" <ji...@apache.org> on 2010/09/01 20:34:54 UTC
[jira] Resolved: (HBASE-1742) Region lost (disabled) when -ROOT-
offline or hosting server dies just before it tells master successful open
[ https://issues.apache.org/jira/browse/HBASE-1742?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
stack resolved HBASE-1742.
--------------------------
Resolution: Won't Fix
Marking as wont' fix. The prob. here was there was no master to receive the open message. Master used update .META. Now RS does since hbase-2692 so this condition should never arise going forward. I added to HBASE-2485 mention that it should add coverage of this scenario -- an open happening while master is down.
> Region lost (disabled) when -ROOT- offline or hosting server dies just before it tells master successful open
> -------------------------------------------------------------------------------------------------------------
>
> Key: HBASE-1742
> URL: https://issues.apache.org/jira/browse/HBASE-1742
> Project: HBase
> Issue Type: Bug
> Reporter: stack
> Fix For: 0.90.0
>
>
> I killed server with -ROOT-. It came back eventually but meantime we'd asked a server to open a region. It failed in the below but then we never try to open the region elsewhere.
> {code}
> 803 2009-08-04 03:21:12,599 [regionserver/XX.XX.XX.140:60020.worker] ERROR org.apache.hadoop.hbase.regionserver.HRegionServer: unable to process message: MSG_REGION_OPEN: TestTable,0916642860,1249356036404
> 804 java.lang.reflect.UndeclaredThrowableException
> 805 at $Proxy2.getRegionInfo(Unknown Source)
> 806 at org.apache.hadoop.hbase.client.HConnectionManager$TableServers.locateRootRegion(HConnectionManager.java:874)
> 807 at org.apache.hadoop.hbase.client.HConnectionManager$TableServers.locateRegion(HConnectionManager.java:515)
> 808 at org.apache.hadoop.hbase.client.HConnectionManager$TableServers.locateRegion(HConnectionManager.java:491)
> 809 at org.apache.hadoop.hbase.client.HConnectionManager$TableServers.locateRegionInMeta(HConnectionManager.java:565)
> 810 at org.apache.hadoop.hbase.client.HConnectionManager$TableServers.locateRegion(HConnectionManager.java:524)
> 811 at org.apache.hadoop.hbase.client.HConnectionManager$TableServers.locateRegion(HConnectionManager.java:491)
> 812 at org.apache.hadoop.hbase.client.HTable.<init>(HTable.java:125)
> 813 at org.apache.hadoop.hbase.RegionHistorian.online(RegionHistorian.java:315)
> 814 at org.apache.hadoop.hbase.regionserver.HRegionServer.openRegion(HRegionServer.java:1564)
> 815 at org.apache.hadoop.hbase.regionserver.HRegionServer$Worker.run(HRegionServer.java:1485)
> 816 at java.lang.Thread.run(Unknown Source)
> 817 Caused by: org.apache.hadoop.ipc.RemoteException: org.apache.hadoop.hbase.NotServingRegionException: -ROOT-,,0
> 818 at org.apache.hadoop.hbase.regionserver.HRegionServer.getRegion(HRegionServer.java:2261)
> 819 at org.apache.hadoop.hbase.regionserver.HRegionServer.getRegionInfo(HRegionServer.java:1741)
> 820 at sun.reflect.GeneratedMethodAccessor2.invoke(Unknown Source)
> 821 at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
> 822 at java.lang.reflect.Method.invoke(Unknown Source)
> 823 at org.apache.hadoop.hbase.ipc.HBaseRPC$Server.call(HBaseRPC.java:650)
> 824 at org.apache.hadoop.hbase.ipc.HBaseServer$Handler.run(HBaseServer.java:913)
> 825
> 826 at org.apache.hadoop.hbase.ipc.HBaseClient.call(HBaseClient.java:720)
> 827 at org.apache.hadoop.hbase.ipc.HBaseRPC$Invoker.invoke(HBaseRPC.java:328)
> 828 ... 12 more
> {code}
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.