Mailing-List: contact hbase-dev-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: hbase-dev@hadoop.apache.org
Message-ID: <1280328392.1208195465523.JavaMail.jira@brutus>
Date: Mon, 14 Apr 2008 10:51:05 -0700 (PDT)
From: "Jim Kellerman (JIRA)" <jira@apache.org>
To: hbase-dev@hadoop.apache.org
Subject: [jira] Updated: (HBASE-11) [hbase] Unexpected exits corrupt DFS
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Jim Kellerman updated HBASE-11:
-------------------------------

    Attachment: patch.txt

Addresses HLog.splitLog encountering EOFException.

> [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
>             Fix For: 0.2.0
>
>         Attachments: patch.txt
>
>
> 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.