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-672) Overload Jobsubmission in core module
Date Tue, 20 Nov 2012 17:32:58 GMT

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

Thomas Jungblut updated HAMA-672:
---------------------------------

    Attachment: HAMA-672_2.patch

Okay, final version.
Testcases work fine, didn't check YARN.

Now YARN jobs can be submitted through the normal BSPJob interface, we might consider adding
a setter for memory- but we can add this later for convenience.

Please check if it also works for you local/classic.
                
> Overload Jobsubmission in core module
> -------------------------------------
>
>                 Key: HAMA-672
>                 URL: https://issues.apache.org/jira/browse/HAMA-672
>             Project: Hama
>          Issue Type: Sub-task
>          Components: bsp core, build , yarn
>            Reporter: Thomas Jungblut
>             Fix For: 0.7.0
>
>         Attachments: HAMA-672_2.patch, HAMA-672.patch
>
>
> introduce new configuration key "bsp.framework.name" which maps to the values: "local,classic,yarn"
> It will change core's BSPJob, so the client can be overloaded via a static mapping of
value->classname. (e.G. local->LocalBSPRunner, classic->BSPMaster and a new implementation
of the JobSubmissionProtocol for YARN).
> So we don't have to introduce a cyclic dependency from core->yarn and yarn->core,
because core->yarn is then decoupled by a jobmission classname mapping.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

Mime
View raw message