Uploaded image for project: 'Hadoop HDFS'
  1. Hadoop HDFS
  2. HDFS-4949 Centralized cache management in HDFS
  3. HDFS-5203

Concurrent clients that add a cache directive on the same path may prematurely uncache from each other.

VotersWatch issueWatchersLinkCloneUpdate Comment AuthorReplace String in CommentUpdate Comment VisibilityDelete Comments
    XMLWordPrintableJSON

Details

    • Sub-task
    • Status: Resolved
    • Major
    • Resolution: Fixed
    • HDFS-4949
    • HDFS-4949
    • namenode
    • None

    Description

      When a client adds a cache directive, we assign it a unique ID and return that ID to the client. If multiple clients add a cache directive for the same path, then we return the same ID. If one client then removes the cache entry for that ID, then it is removed for all clients. Then, when this change becomes visible in subsequent cache reports, the datanodes may munlock the block before the other clients are done with it.

      Attachments

        1. HDFS-5203.1.patch
          28 kB
          Chris Nauroth
        2. HDFS-5203.2.patch
          7 kB
          Chris Nauroth
        3. HDFS-5203.3.patch
          16 kB
          Chris Nauroth

        Issue Links

        Activity

          This comment will be Viewable by All Users Viewable by All Users
          Cancel

          People

            cnauroth Chris Nauroth
            cnauroth Chris Nauroth
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved:

              Slack

                Issue deployment