Uploaded image for project: 'Hadoop Map/Reduce'
  1. Hadoop Map/Reduce
  2. MAPREDUCE-65

TaskTrackers never (re)connect back to the JobTracker if the JobTracker node/machine is changed

    XMLWordPrintableJSON

Details

    • Bug
    • Status: Resolved
    • Major
    • Resolution: Won't Fix
    • None
    • None
    • None
    • None

    Description

      I tried the following
      1) Started a hadoop cluster.
      2) Killed the JT
      3) Selected a new node for starting JT.
      4) Changed the entry on the tasktracker to reflect the new (old) hostname to (new) ip mapping. Checked if the tracker node correctly resolves the hostname to the new ip.
      5) Start the JT on the new node
      The tasktracker fails to connect to the new jobtracker. It seems that the hostname resolution remains stale and is never updated.

      Attachments

        Issue Links

          is part of

          New Feature - A new feature of the product, which has yet to be developed. MAPREDUCE-225 Fault tolerant Hadoop Job Tracker

          • Major - Major loss of function.
          • Resolved
          is related to

          New Feature - A new feature of the product, which has yet to be developed. MAPREDUCE-2288 JT Availability

          • Major - Major loss of function.
          • Resolved

          Activity

            People

              Unassigned Unassigned
              amar_kamat Amar Kamat
              Votes:
              0 Vote for this issue
              Watchers:
              10 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: