Mailing-List: contact issues-help@hbase.apache.org; run by ezmlm
Precedence: bulk
Date: Thu, 3 Feb 2011 01:08:29 +0000 (UTC)
From: "stack (JIRA)" <jira@apache.org>
To: issues@hbase.apache.org
Message-ID: 
 <1478401145.6542.1296695309025.JavaMail.tomcat@hel.zones.apache.org>
In-Reply-To: 
 <668787297.6369.1296690509343.JavaMail.tomcat@hel.zones.apache.org>
Subject: [jira] Updated: (HBASE-3502) Can't open region because can't open
 .regioninfo because AlreadyBeingCreatedException
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


     [ https://issues.apache.org/jira/browse/HBASE-3502?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

stack updated HBASE-3502:
-------------------------

    Attachment: 3502.txt

Does simple create in the region dir of .regioninfo.  Adds timestamp to tmpfile as primitive guard against filename classes in tmpdir.  After successful write, does rename.

> Can't open region because can't open .regioninfo because AlreadyBeingCreatedException
> -------------------------------------------------------------------------------------
>
>                 Key: HBASE-3502
>                 URL: https://issues.apache.org/jira/browse/HBASE-3502
>             Project: HBase
>          Issue Type: Bug
>            Reporter: stack
>            Priority: Critical
>             Fix For: 0.90.1
>
>         Attachments: 3502.txt
>
>
> Testing killing .META. I tripped over this one.  Last thing seen on regionserver killed was:
> {code}
> 2011-02-02 21:44:48,379 DEBUG org.apache.hadoop.hbase.regionserver.HRegion: Instantiated TestTable,0591556500,1296683085472.76c9a32c5f068d16240e42a15fed8417.
> {code}
> ... which means we could have been inside checkRegioninfoOnFilesystem when we were killed.
> This tries to create the .regioninfo file.  Seems like that was started over at the NN but then the RS died shortly afterward.  Its stopping the Region opening.  I suppose I could try and open it for append to shut it then reopen?

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