Mailing-List: contact issues-help@hbase.apache.org; run by ezmlm
Precedence: bulk
Date: Mon, 31 Oct 2011 22:43:32 +0000 (UTC)
From: "stack (Updated) (JIRA)" <jira@apache.org>
To: issues@hbase.apache.org
Message-ID: 
 <347374587.43064.1320101012162.JavaMail.tomcat@hel.zones.apache.org>
In-Reply-To: 
 <1298340323.8491.1318003290609.JavaMail.tomcat@hel.zones.apache.org>
Subject: [jira] [Updated] (HBASE-4553) The update of .tableinfo is not
 atomic; we remove then rename
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

stack updated HBASE-4553:
-------------------------

    Attachment: 3446-v8.txt

Change .tableinfo naming so its now .tableinfo.SEQUENCEID.  The sequenceid always rolls forward (next seqid is based off the old one).  This removes hole where we could have no .tableinfo in case where editors crash at inopportune time (TODO: Same for .regioninfo -- should be a single .regioninfo rather than one per region).

Bulk of patch is moving TableDescriptor utility out of FSUtils into the FSTableDescriptors class.


> The update of .tableinfo is not atomic; we remove then rename
> -------------------------------------------------------------
>
>                 Key: HBASE-4553
>                 URL: https://issues.apache.org/jira/browse/HBASE-4553
>             Project: HBase
>          Issue Type: Task
>            Reporter: stack
>            Priority: Critical
>             Fix For: 0.92.0
>
>         Attachments: 3446-v8.txt, 4553-v5.txt, HBase-4553-TestAvroServer.patch
>
>
> This comes of HBASE-4547.  The rename in 0.20 hdfs fails if file exists already.  In 0.20+ its better but still 'some' issues if existing reader when file is renamed.  This issue is about fixing this (though we depend on fix first being in hdfs).

--
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