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 "Doug Judd (JIRA)" <ji...@apache.org> on 2009/02/27 21:45:13 UTC

[jira] Created: (HADOOP-5359) HDFS soft lease limit should be configurable per-file

HDFS soft lease limit should be configurable per-file
-----------------------------------------------------

                 Key: HADOOP-5359
                 URL: https://issues.apache.org/jira/browse/HADOOP-5359
             Project: Hadoop Core
          Issue Type: Bug
          Components: dfs
    Affects Versions: 0.19.1
         Environment: All operating systems
            Reporter: Doug Judd


In Hypertable, there is a process called the RangeServer which is responsible for handling updates and queries on portions (ranges) of a database table.  When an update arrives at the RangeServer, it first gets written to a commit log and then it goes into an in-memory table structure.  If at any time, the RangeServer dies, when it comes back up, it replays the commit log to reconstruct the state of the in-memory table structure.  As it stands now, when the RangeServer comes up, it cannot read the commit log file until the soft lease limit has expired.  This causes the RangeServer to hang with all of the ranges that it was managing unaccessible.

We would like to be able to configure the soft lease limit per-file so that we can set the limit to 0 for our commit log files.  That would allow Hypertable to recover immediately after a crash.


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

[jira] Updated: (HADOOP-5359) HDFS soft lease limit should be configurable per-file

Posted by "Doug Judd (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/HADOOP-5359?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Doug Judd updated HADOOP-5359:
------------------------------

    Fix Version/s: 0.20.0

> HDFS soft lease limit should be configurable per-file
> -----------------------------------------------------
>
>                 Key: HADOOP-5359
>                 URL: https://issues.apache.org/jira/browse/HADOOP-5359
>             Project: Hadoop Core
>          Issue Type: Bug
>          Components: dfs
>    Affects Versions: 0.19.1
>         Environment: All operating systems
>            Reporter: Doug Judd
>             Fix For: 0.20.0
>
>
> In Hypertable, there is a process called the RangeServer which is responsible for handling updates and queries on portions (ranges) of a database table.  When an update arrives at the RangeServer, it first gets written to a commit log and then it goes into an in-memory table structure.  If at any time, the RangeServer dies, when it comes back up, it replays the commit log to reconstruct the state of the in-memory table structure.  As it stands now, when the RangeServer comes up, it cannot read the commit log file until the soft lease limit has expired.  This causes the RangeServer to hang with all of the ranges that it was managing unaccessible.
> We would like to be able to configure the soft lease limit per-file so that we can set the limit to 0 for our commit log files.  That would allow Hypertable to recover immediately after a crash.

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