Mailing-List: contact issues-help@hbase.apache.org; run by ezmlm
Precedence: bulk
Date: Fri, 2 Dec 2011 17:59:40 +0000 (UTC)
From: "Jean-Daniel Cryans (Commented) (JIRA)" <jira@apache.org>
To: issues@hbase.apache.org
Message-ID: 
 <836194177.35428.1322848780521.JavaMail.tomcat@hel.zones.apache.org>
In-Reply-To: 
 <1771126705.29222.1322703819879.JavaMail.tomcat@hel.zones.apache.org>
Subject: [jira] [Commented] (HBASE-4921) HTable initialization looks for
 EMPTY_START_ROW
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


    [ https://issues.apache.org/jira/browse/HBASE-4921?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13161754#comment-13161754 ] 

Jean-Daniel Cryans commented on HBASE-4921:
-------------------------------------------

My understanding is that this is used to check the existence of the table, whether it's disabled or not shouldn't really matter. This is not the only place where the region offline exception is thrown all the way up, admin.split does the same thing.

What exactly was the stack trace you saw Pritam?
                
> 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