Details

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

      Description

      This was reported by Chris Nauroth and Brandon Li, and Stephen Chu repro'd it too.

      If you add a new caching directive then remove it, the Namenode will sometimes get stuck in a loop where it sends DNA_CACHE and then DNA_UNCACHE repeatedly to the datanodes where the data was previously cached.

      1. hdfs-5589-1.patch
        10 kB
        Andrew Wang
      2. hdfs-5589-2.patch
        19 kB
        Andrew Wang

        Issue Links

          Activity

            People

            • Assignee:
              Andrew Wang
              Reporter:
              Andrew Wang
            • Votes:
              0 Vote for this issue
              Watchers:
              7 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved:

                Development