Uploaded image for project: 'Samza'
  1. Samza
  2. SAMZA-770

HttpServer uses getHostAddress instead of getHostName to build URL

    XMLWordPrintableJSON

    Details

    • Type: Bug
    • Status: Resolved
    • Priority: Blocker
    • Resolution: Fixed
    • Affects Version/s: 0.10.0
    • Fix Version/s: 0.10.0
    • Component/s: None
    • Labels:
      None

      Description

      Here's the scene:

      I am running my Samza (0.9.0) job in a YARN (2.7.1) cluster that is running in docker (1.7.1) and networked together using Weave (1.1.0)

      When the YARN AM starts up the first Samza container on the master node it starts the Job Coordinator's HttpServer using the IP of the 'eth0' network interface because that is the first valid interface that it found.

      When the second Samza container is started on the slave node, it tries to fetch configuration from the Coordinator URL, but we get "Connection Refused" because it cannot communicate with the master node on the IP assigned to the master's 'eth0' network interface.

      Essentially we need the Coordinator URL to use the hostname, which will resolve to the correct IP on the master's 'ethwe' network interface from any machine on the Weave network.

      Any thoughts?

        Attachments

        1. SAMZA-2.0.patch
          2 kB
          Michael Martin

          Activity

            People

            • Assignee:
              anaerobic Michael Martin
              Reporter:
              anaerobic Michael Martin
            • Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: