You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@hbase.apache.org by "Jim Kellerman (JIRA)" <ji...@apache.org> on 2008/02/24 03:05:19 UTC

[jira] Assigned: (HBASE-11) [hbase] Unexpected exits corrupt DFS

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

Jim Kellerman reassigned HBASE-11:
----------------------------------

    Assignee: Jim Kellerman

> [hbase] Unexpected exits corrupt DFS
> ------------------------------------
>
>                 Key: HBASE-11
>                 URL: https://issues.apache.org/jira/browse/HBASE-11
>             Project: Hadoop HBase
>          Issue Type: Bug
>          Components: regionserver
>            Reporter: Bryan Duxbury
>            Assignee: Jim Kellerman
>
> When a RegionServer exits unexpectedly, it often leaves its DFS files open. In the case of the redo log, this can result in a zero-length file, which a newly started RegionServer will be unable to read, causing it to exit again. It also causes DFS corruption, requiring the admin to run a dfs fsck -delete before HBase can be restarted.

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