hama-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Thomas Jungblut (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (HAMA-592) Groom starts with reversed DNS not with configured hostname
Date Mon, 18 Jun 2012 07:36:42 GMT

     [ https://issues.apache.org/jira/browse/HAMA-592?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Thomas Jungblut updated HAMA-592:
---------------------------------

          Component/s: bsp core
             Priority: Blocker  (was: Major)
    Affects Version/s: 0.5.0
        Fix Version/s: 0.5.0
    
> 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
>            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.
> 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

        

Mime
View raw message