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

Remove dfs.namenode.caching.enabled and improve CRM locking

    XMLWordPrintableJSON

    Details

    • Type: Sub-task
    • Status: Closed
    • Priority: Major
    • Resolution: Fixed
    • Affects Version/s: 3.0.0-alpha1
    • Fix Version/s: 2.3.0
    • Component/s: namenode
    • Labels:
      None
    • Target Version/s:

      Description

      We can remove dfs.namenode.caching.enabled and simply always enable caching, similar to how we do with snapshots and other features. The main overhead is the size of the cachedBlocks GSet. However, we can simply make the size of this GSet configurable, and people who don't want caching can set it to a very small value.

        Attachments

        1. HDFS-5651.009.patch
          36 kB
          Colin McCabe
        2. HDFS-5651.008.patch
          35 kB
          Colin McCabe
        3. HDFS-5651.006.patch
          32 kB
          Colin McCabe
        4. HDFS-5651.006.patch
          32 kB
          Colin McCabe
        5. HDFS-5651.004.patch
          14 kB
          Colin McCabe
        6. HDFS-5651.003.patch
          15 kB
          Colin McCabe
        7. HDFS-5651.002.patch
          13 kB
          Colin McCabe
        8. HDFS-5651.001.patch
          11 kB
          Colin McCabe

          Activity

            People

            • Assignee:
              cmccabe Colin McCabe
              Reporter:
              cmccabe Colin McCabe
            • Votes:
              0 Vote for this issue
              Watchers:
              10 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: