Mailing-List: contact issues-help@hbase.apache.org; run by ezmlm
Precedence: bulk
Date: Mon, 18 Jul 2011 05:10:59 +0000 (UTC)
From: "ramkrishna.s.vasudevan (JIRA)" <jira@apache.org>
To: issues@hbase.apache.org
Message-ID: 
 <656382049.21788.1310965859956.JavaMail.tomcat@hel.zones.apache.org>
In-Reply-To: 
 <1131548735.2875.1310390760248.JavaMail.tomcat@hel.zones.apache.org>
Subject: [jira] [Commented] (HBASE-4083) If Enable table is not completed
 and is partial, then scanning of the table is not working
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

ramkrishna.s.vasudevan commented on HBASE-4083:
-----------------------------------------------

@Ted, thanks for the review.
We need to delete the node in zookeeper which is in offline state.  Because as part of recovery when we try to enable the table , the regions of the table  may be already onlined so we just try to delete the node created for that region.
If we dont delete the node, scans can be performed but if we try to disable the table it may not work as already the node is created in zookeeper.
So thats why any failure while deleting the node i thouhgt of aborting the master which is the way we have handled in 
public void offlineDisabledRegion(HRegionInfo regionInfo) and in 
OpenedRegionHandler.process() api.
Please provide your comments.

> If Enable table is not completed and is partial, then scanning of the table is not working 
> -------------------------------------------------------------------------------------------
>
>                 Key: HBASE-4083
>                 URL: https://issues.apache.org/jira/browse/HBASE-4083
>             Project: HBase
>          Issue Type: Bug
>            Reporter: ramkrishna.s.vasudevan
>            Assignee: ramkrishna.s.vasudevan
>         Attachments: HBASE-4083-1.patch
>
>
> Consider the following scenario
> Start the Master, Backup master and RegionServer.
> Create a table which in turn creates a region.
> Disable the table.
> Enable the table again. 
> Kill the Active master exactly at the point before the actual region assignment is started.
> Restart or switch master.
> Scan the table.
> NotServingRegionExcepiton is thrown.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira