[
https://issues.apache.org/jira/browse/HAMA-592?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Edward J. Yoon reassigned HAMA-592:
-----------------------------------
Assignee: Edward J. Yoon
> Groom starts with reversed DNS not with configured hostname
> -----------------------------------------------------------
>
> Key: HAMA-592
> URL: https://issues.apache.org/jira/browse/HAMA-592
> Project: Hama
> Issue Type: Bug
> Components: bsp core
> Affects Versions: 0.5.0
> Reporter: Thomas Jungblut
> Assignee: Edward J. Yoon
> Priority: Blocker
> Fix For: 0.5.0
>
>
> bq.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:
> bq.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.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
