You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@hbase.apache.org by "stack (JIRA)" <ji...@apache.org> on 2008/09/04 20:17:44 UTC
[jira] Created: (HBASE-869) On split, if failure updating of
.META., table subsequently broke
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
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 closed.
+ 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.
[jira] Assigned: (HBASE-869) On split, if failure updating of
.META., table subsequently broke
Posted by "Andrew Purtell (JIRA)" <ji...@apache.org>.
[ 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 closed.
> + 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.
[jira] Updated: (HBASE-869) On split, if failure updating of
.META., table subsequently broke
Posted by "Jim Kellerman (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HBASE-869?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jim Kellerman updated HBASE-869:
--------------------------------
Fix Version/s: 0.20.0
> 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
> 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 closed.
> + 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.
[jira] Updated: (HBASE-869) On split, if failure updating of
.META., table subsequently broke
Posted by "stack (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HBASE-869?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
stack updated HBASE-869:
------------------------
Fix Version/s: (was: 0.20.0)
This is a 0.2.0 issue and the provocation has been fixed. This could still happen but rare event I'd say. Will leave it open but move it out of 0.20.0.
> 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
>
> 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 closed.
> + 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.