Uploaded image for project: 'Hama'
  1. Hama
  2. HAMA-592

Groom starts with reversed DNS not with configured hostname

    XMLWordPrintableJSON

Details

    • Bug
    • Status: Resolved
    • Blocker
    • Resolution: Won't Fix
    • 0.5.0
    • 0.5.0
    • bsp core
    • None

    Description

      12/06/17 23:03:43 ERROR bsp.TaskInProgress: Could not find groom for location: localhost ; active grooms: [vesta.apache.org]

      Okay, so DFS just uses what has been configured, we have to do it for the groom as well.

      This is very easy reproducable:

      first edit your /etc/hosts to:
      127.0.0.1 localhost.localdomain localhost

      and do a "hostname localhost"

      Now you can run this on the hama trunk:
      mvn clean install -pl graph

      Which yields to failure:

      12/06/18 10:06:55 ERROR bsp.TaskInProgress: Could not find groom for location: localhost ; active grooms: [localhost.localdomain]

      Which means the groom has done a DNS lookup for the hostname localhost, which yields to localhost.localdomain.

      You can fix that by using no duplicate hostname with a domain:
      127.0.0.1 localhost

      This is really uncommon and thus we should fix that ASAP.
      Also see HAMA-583 for more information on cloud environments.

      Attachments

        Issue Links

          Activity

            People

              udanax Edward J. Yoon
              thomas.jungblut Thomas Jungblut
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: