Hadoop Common
  1. Hadoop Common
  2. HADOOP-1202

Jobtracker & Namenode can only bind to one interface

    Details

    • Type: Bug Bug
    • Status: Open
    • Priority: Major Major
    • Resolution: Unresolved
    • Affects Version/s: None
    • Fix Version/s: None
    • Component/s: None
    • Labels:
      None

      Description

      There is no way to tell the jobtracker & namenode to listen on more than one interface. Because of firewall rules etc., my datanodes/tasktrackers and human users live on different networks, and so talk to the jobtracker/namenode on different interfaces.

      Currently, the namenode will bind to the hostname specified in configuration in fs.default.name, and the jobtracker will bind to the hostname in mapred.job.tracker. These names are also reported to datanode and tasktracker clients.

      Consequently, putting a fqhn in these fields causes the server to only listen on the interface serving that fqhn. Putting 0.0.0.0 in these fields causes the server to report 0.0.0.0 as its address to clients, which confuses the clients and causes them to fail.

      1. bind-all-addresses.patch
        3 kB
        Michael Bieniosek
      2. bind-all-addresses-2.patch
        3 kB
        Fredrik Hedberg

        Issue Links

          Activity

          Michael Bieniosek created issue -
          Michael Bieniosek made changes -
          Field Original Value New Value
          Status Open [ 1 ] Patch Available [ 10002 ]
          Michael Bieniosek made changes -
          Attachment bind-all-addresses.patch [ 12354936 ]
          Michael Bieniosek made changes -
          Description Currently, the namenode will bind to the hostname in fs.default.name, and the jobtracker will bind to the hostname in mapred.job.tracker. These names are also reported to datanode and tasktracker clients.

          Consequently, putting a fqhn in these fields causes the server to only listen on the interface serving that fqhn. Putting 0.0.0.0 in these fields causes the server to report 0.0.0.0 as its address to clients, which confuses the clients and causes them to fail.
          Currently, the namenode will bind to the hostname specified in configuration in fs.default.name, and the jobtracker will bind to the hostname in mapred.job.tracker. These names are also reported to datanode and tasktracker clients.

          Consequently, putting a fqhn in these fields causes the server to only listen on the interface serving that fqhn. Putting 0.0.0.0 in these fields causes the server to report 0.0.0.0 as its address to clients, which confuses the clients and causes them to fail.
          Tom White made changes -
          Status Patch Available [ 10002 ] Open [ 1 ]
          Jeremy made changes -
          Link This issue is related to HADOOP-1265 [ HADOOP-1265 ]
          Michael Bieniosek made changes -
          Summary Need to be able to set jobtracker & namenode to bind to 0.0.0.0 Jobtracker & Namenode can only bind to one interface
          Description Currently, the namenode will bind to the hostname specified in configuration in fs.default.name, and the jobtracker will bind to the hostname in mapred.job.tracker. These names are also reported to datanode and tasktracker clients.

          Consequently, putting a fqhn in these fields causes the server to only listen on the interface serving that fqhn. Putting 0.0.0.0 in these fields causes the server to report 0.0.0.0 as its address to clients, which confuses the clients and causes them to fail.
          There is no way to tell the jobtracker & namenode to listen on more than one interface. Because of firewall rules etc., my datanodes/tasktrackers and human users live on different networks, and so talk to the jobtracker/namenode on different interfaces.

          Currently, the namenode will bind to the hostname specified in configuration in fs.default.name, and the jobtracker will bind to the hostname in mapred.job.tracker. These names are also reported to datanode and tasktracker clients.

          Consequently, putting a fqhn in these fields causes the server to only listen on the interface serving that fqhn. Putting 0.0.0.0 in these fields causes the server to report 0.0.0.0 as its address to clients, which confuses the clients and causes them to fail.
          Fredrik Hedberg made changes -
          Link This issue blocks HADOOP-1638 [ HADOOP-1638 ]
          Fredrik Hedberg made changes -
          Attachment bind-all-addresses-2.patch [ 12362288 ]
          Gavin made changes -
          Link This issue blocks HADOOP-1638 [ HADOOP-1638 ]
          Gavin made changes -
          Link This issue is depended upon by HADOOP-1638 [ HADOOP-1638 ]

            People

            • Assignee:
              Unassigned
              Reporter:
              Michael Bieniosek
            • Votes:
              4 Vote for this issue
              Watchers:
              8 Start watching this issue

              Dates

              • Created:
                Updated:

                Development