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

Posted to common-dev@hadoop.apache.org by "Jim Kellerman (JIRA)" <ji...@apache.org> on 2007/10/05 06:27:51 UTC

[jira] Updated: (HADOOP-1937) [hbase] when the master times out a region server's lease, it is too aggressive in reclaiming the server's log

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

Jim Kellerman updated HADOOP-1937:
----------------------------------

    Status: Patch Available  (was: Open)

> [hbase] when the master times out a region server's lease, it is too aggressive in reclaiming the server's log
> --------------------------------------------------------------------------------------------------------------
>
>                 Key: HADOOP-1937
>                 URL: https://issues.apache.org/jira/browse/HADOOP-1937
>             Project: Hadoop
>          Issue Type: Bug
>          Components: contrib/hbase
>    Affects Versions: 0.15.0
>            Reporter: Jim Kellerman
>            Assignee: Jim Kellerman
>             Fix For: 0.15.0
>
>         Attachments: patch.txt
>
>
> When a region server's lease times out, the master immediately begins trying to split the server's log file. There have been cases where a region server was just a little late reporting to the master and the master had already started trying to reclaim the server's log, even though the server was still writing to it. 
> There needs to be some kind of "grace period" in which, if the region server reports in, the master re-instates the server. If the "grace period" expires, then the master should start processing the server's log.

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