Mailing-List: contact hama-dev-help@incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: hama-dev@incubator.apache.org
Date: Wed, 19 Oct 2011 15:07:10 +0000 (UTC)
From: "Thomas Jungblut (Issue Comment Edited) (JIRA)" <jira@apache.org>
To: hama-dev@incubator.apache.org
Message-ID: 
 <626497354.10701.1319036830604.JavaMail.tomcat@hel.zones.apache.org>
In-Reply-To: 
 <1800030880.6739.1318953070631.JavaMail.tomcat@hel.zones.apache.org>
Subject: [jira] [Issue Comment Edited] (HAMA-457) Refactoring of BSPPeerImpl
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


    [ https://issues.apache.org/jira/browse/HAMA-457?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13130670#comment-13130670 ] 

Thomas Jungblut edited comment on HAMA-457 at 10/19/11 3:05 PM:
----------------------------------------------------------------

Ah great, thanks.
Do you updated the default configuration on every host?
Then the configuration should contain the classname to instantiate.

Strangely, the configuration should contain the jobfile, which should contain the configuration on the master host.
But I fix the nullpointer exception.
                
      was (Author: thomas.jungblut):
    Ah great, thanks.
Do you updated the default configuration on every host?
Then the configuration should contain the classname to instantiate.
                  
> Refactoring of BSPPeerImpl
> --------------------------
>
>                 Key: HAMA-457
>                 URL: https://issues.apache.org/jira/browse/HAMA-457
>             Project: Hama
>          Issue Type: Improvement
>    Affects Versions: 0.3.0
>            Reporter: Thomas Jungblut
>            Assignee: Thomas Jungblut
>             Fix For: 0.4.0
>
>         Attachments: HAMA-457.patch, HAMA-457_v2.patch, HAMA-457_v3.patch
>
>
> Extract a sync service which allows the user to implement and configure their own services.

--
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