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

Posted to hdfs-issues@hadoop.apache.org by "Igloo (JIRA)" <ji...@apache.org> on 2018/03/15 03:02:00 UTC

[jira] [Created] (HDFS-13288) Why we don't add a harder lease expiration limit.

Igloo created HDFS-13288:
----------------------------

             Summary: Why we don't add a harder lease expiration limit.
                 Key: HDFS-13288
                 URL: https://issues.apache.org/jira/browse/HDFS-13288
             Project: Hadoop HDFS
          Issue Type: Improvement
          Components: namenode
    Affects Versions: 2.6.5
            Reporter: Igloo


Currently there exists a soft expire timeout(1 minutes by default) and hard expire timeout(60 minutes by default). 

On our production environment. Some client began writing a file long time(more than one year) ago, when writing finished and tried to close the output stream, the client failed closing it (for some IOException. etc. ).  But the client process is a background service, it doesn't exit. So the lease doesn't released for more than one year.

The problem is the lease for the file is occupied, we have to call recover lease on the file.

So I am wondering why we don't add a more harder lease expire timeout, when a lease lasts too long (maybe one month), revoke it.  

 



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

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