Uploaded image for project: 'Hadoop HDFS'
  1. Hadoop HDFS
  2. HDFS-11945

Internal lease recovery may not be retried for a long time

    XMLWordPrintableJSON

Details

    • Bug
    • Status: Resolved
    • Major
    • Resolution: Fixed
    • None
    • 3.0.0-alpha4, 2.8.2
    • namenode
    • None
    • Reviewed

    Description

      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.

      Attachments

        1. HDFS-11945.trunk.patch
          7 kB
          Kihwal Lee
        2. HDFS-11945.branch-2.v2.patch
          7 kB
          Kihwal Lee
        3. HDFS-11945.trunk.v2.patch
          7 kB
          Kihwal Lee

        Activity

          People

            kihwal Kihwal Lee
            kihwal Kihwal Lee
            Votes:
            0 Vote for this issue
            Watchers:
            10 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: