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] [Commented] (HAMA-670) Hama YARN
Date Fri, 16 Nov 2012 16:56:13 GMT

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

Thomas Jungblut commented on HAMA-670:

A bit more detailed answer, in addition to my "there is no cluster status" on the mailing

The ClusterStatus exists to get a notion of how many tasks slots are available and how many
tasks are running, besides the info about the grooms.
So in YARN, you don't have these informations, why? Because you should not care about this
in the client. So our BSPClient should not be aware of the cluster in YARN. Which sadly makes
HAMA-672 useless because you have to override the job submission mechanism, because we require
the number of tasks before submitting to the cluster. 

In the end, this functionality must be added to the ApplicationMaster, because it can decide
how much container need to launch (although he should also be not aware of the resources in
the cluster).
Looks like the whole task will be a bit more ugly than I initially thought it would be..
> Hama YARN
> ---------
>                 Key: HAMA-670
>                 URL: https://issues.apache.org/jira/browse/HAMA-670
>             Project: Hama
>          Issue Type: Umbrella
>          Components: bsp core, build , yarn
>    Affects Versions: 0.6.0
>            Reporter: Thomas Jungblut
>             Fix For: 0.7.0

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

View raw message