Uploaded image for project: 'Hadoop Common'
  1. Hadoop Common
  2. HADOOP-1762

Namenode does not need to store storageID and datanodeID persistently

    XMLWordPrintableJSON

Details

    • Improvement
    • Status: Closed
    • Major
    • Resolution: Fixed
    • 0.14.0
    • 0.15.0
    • None
    • None

    Description

      Currently Namenode stores all the storage-ids it generates since the beginning (since last format). It allocates a new storageID everytime a new datanode comes online. It also stores all the known datanode ids since the beginning.

      It would be better if Namenode did not have to keep track of these. I will describe a proposal in the next comment.

      This has implecations regd how Namenode helps administrators identify 'dead datanodes' etc. These issues are addressed in HADOOP-1138.

      Attachments

        1. HADOOP-1762-Opt2.patch
          8 kB
          Raghu Angadi
        2. HADOOP-1762-Opt2.patch
          8 kB
          Raghu Angadi
        3. HADOOP-1762-Opt2.patch
          8 kB
          Raghu Angadi
        4. HADOOP-1762-Opt2.patch
          8 kB
          Raghu Angadi
        5. HADOOP-1762-Opt2.patch
          9 kB
          Raghu Angadi
        6. HADOOP-1762-Opt2.patch
          10 kB
          Raghu Angadi
        7. HADOOP-1762.patch
          9 kB
          Raghu Angadi
        8. HADOOP-1762.patch
          9 kB
          Raghu Angadi

        Issue Links

          relates to

          Sub-task - The sub-task of the issue HDFS-4702 remove namesystem lock from DatanodeManager#fetchDatanodes

          • Major - Major loss of function.
          • Resolved

          Activity

            People

              rangadi Raghu Angadi
              rangadi Raghu Angadi
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: