[
https://issues.apache.org/jira/browse/HBASE-4921?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13161804#comment-13161804
]
Pritam Damania commented on HBASE-4921:
---------------------------------------
@Jean-Daniel Cryans
Here is the stack trace :
Exception in thread "main"
org.apache.hadoop.hbase.client.RegionOfflineException: region offline:
VerificationTest_DummyTable,,1322854092301.58a6099fa8fd53eb23c6329cf9fc46fe.
at
org.apache.hadoop.hbase.client.HConnectionManager$TableServers.locateRegionInMeta(HConnectionManager.java:839)
at
org.apache.hadoop.hbase.client.HConnectionManager$TableServers.locateRegion(HConnectionManager.java:694)
at
org.apache.hadoop.hbase.client.HConnectionManager$TableServers.locateRegion(HConnectionManager.java:661)
at org.apache.hadoop.hbase.client.HTable.<init>(HTable.java:137)
> HTable initialization looks for EMPTY_START_ROW
> -----------------------------------------------
>
> Key: HBASE-4921
> URL: https://issues.apache.org/jira/browse/HBASE-4921
> Project: HBase
> Issue Type: Bug
> Affects Versions: 0.90.4
> Reporter: Pritam Damania
>
> The HTable initialization does something like this :
> {code}this.connection.locateRegion(tableName,
> HConstants.EMPTY_START_ROW);{code}
> What is the rationale behind this ? What would happen if this region is in
> flight ? I ran into a problem where I disabled the first region of the table
> and now I can't create an HTable instance to this table.
> Disabling the first region is like disabling the entire table from a client
> perspective. I feel this is not the correct behavior.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
