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

Namenode should synchronously resolve a datanode's network location when the datanode registers

    XMLWordPrintableJSON

Details

    • Improvement
    • Status: Closed
    • Major
    • Resolution: Fixed
    • 0.18.0
    • 0.19.0
    • None
    • None
    • Reviewed

    Description

      Release 0.18.0 removes the rpc timeout. So the namenode is ok to resolve a datanode's network location when the datanode registers. This could remove quite a lot of unnecessary code in both datanode and namenode to handle asynchronous network location resolution and avoid many potential bugs.

      Attachments

        1. netResolution.patch
          17 kB
          Hairong Kuang
        2. netResolution1.patch
          23 kB
          Hairong Kuang
        3. netResolution2.patch
          22 kB
          Hairong Kuang
        4. netResolution3.patch
          27 kB
          Hairong Kuang
        5. netResolution4.patch
          27 kB
          Hairong Kuang
        6. netResolution5.patch
          32 kB
          Hairong Kuang
        7. netResolution6.patch
          33 kB
          Hairong Kuang

        Issue Links

          incorporates

          Bug - A problem which impairs or prevents the functions of the product. HADOOP-3709 Lock hierarchy violation in namenode while handling hearbeats

          • Major - Major loss of function.
          • Closed

          Activity

            People

              hairong Hairong Kuang
              hairong Hairong Kuang
              Votes:
              0 Vote for this issue
              Watchers:
              4 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: