hbase-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Andrew Purtell (JIRA)" <j...@apache.org>
Subject [jira] Assigned: (HBASE-869) On split, if failure updating of .META., table subsequently broke
Date Thu, 30 Apr 2009 22:43:30 GMT

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

Andrew Purtell reassigned HBASE-869:

    Assignee: stack

Assigned to stack at his request.

> On split, if failure updating of .META., table subsequently broke
> -----------------------------------------------------------------
>                 Key: HBASE-869
>                 URL: https://issues.apache.org/jira/browse/HBASE-869
>             Project: Hadoop HBase
>          Issue Type: Bug
>            Reporter: stack
>            Assignee: stack
>             Fix For: 0.20.0
> On pset cluster -- running 0.2.0 -- I saw the following:
> + Deadlock on server carrying .META. made the .META. table inaccessible (deadlock has
been fixed)
> + Out on a regionserver, we split; two new daughters are created and parent region is
> + Regionserver fails to update the .META. with change in parent state and addition of
two new daughter regions
> Restarting the server carrying .META. got us over the deadlock but subsequently, the
parent region is no longer online nor its replacements.
> Attempting restart of regionserver to see if parent will come back on line (since it
was not 'offlined' in .META. should come back on line again and resplit).  Ugly will be the
fact that the filesystem has some trash in it -- the new daughter regions.
> To consider: Do not close the parent until the .META. has been successfully updated.
 Also, if .META. update fails, remove daughter regions.

This message is automatically generated by JIRA.
You can reply to this email to add a comment to the issue online.

View raw message