hadoop-hdfs-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hudson (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HDFS-11945) Internal lease recovery may not be retried for a long time
Date Thu, 08 Jun 2017 22:06:18 GMT

    [ https://issues.apache.org/jira/browse/HDFS-11945?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16043523#comment-16043523

Hudson commented on HDFS-11945:

SUCCESS: Integrated in Jenkins build Hadoop-trunk-Commit #11846 (See [https://builds.apache.org/job/Hadoop-trunk-Commit/11846/])
HDFS-11945. Internal lease recovery may not be retried for a long time. (liuml07: rev 1a33c9d58927186c2f219a5ecb5f1573801823ad)
* (edit) hadoop-hdfs-project/hadoop-hdfs/src/test/java/org/apache/hadoop/hdfs/server/namenode/TestFileTruncate.java
* (edit) hadoop-hdfs-project/hadoop-hdfs/src/test/java/org/apache/hadoop/hdfs/TestLeaseRecovery2.java
* (edit) hadoop-hdfs-project/hadoop-hdfs/src/main/java/org/apache/hadoop/hdfs/server/namenode/LeaseManager.java
* (edit) hadoop-hdfs-project/hadoop-hdfs/src/test/java/org/apache/hadoop/hdfs/server/namenode/TestLeaseManager.java

> Internal lease recovery may not be retried for a long time
> ----------------------------------------------------------
>                 Key: HDFS-11945
>                 URL: https://issues.apache.org/jira/browse/HDFS-11945
>             Project: Hadoop HDFS
>          Issue Type: Bug
>          Components: namenode
>            Reporter: Kihwal Lee
>            Assignee: Kihwal Lee
>             Fix For: 3.0.0-alpha4, 2.8.2
>         Attachments: HDFS-11945.branch-2.v2.patch, HDFS-11945.trunk.patch, HDFS-11945.trunk.v2.patch
> Lease is assigned per client who is identified by its holder ID or client ID, thus a
renewal or an expiration of a lease affects all files being written by the client.
> When a client/writer dies without closing a file, its lease expires in one hour (hard
limit) and the namenode tries to recover the lease. As a part of the process, the namenode
takes the ownership of the lease and renews it. If the recovery does not finish successfully,
the lease will expire in one hour and the namenode will try again to recover the lease.
> However, if a file system has another lease expiring within the hour, the recovery attempt
for the lease will push forward the expiration of the lease held by the namenode.  This causes
failed lease recoveries to be not retried for a long time. We have seen it happening for days.

This message was sent by Atlassian JIRA

To unsubscribe, e-mail: hdfs-issues-unsubscribe@hadoop.apache.org
For additional commands, e-mail: hdfs-issues-help@hadoop.apache.org

View raw message