You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@mesos.apache.org by "Till Toenshoff (JIRA)" <ji...@apache.org> on 2016/10/28 16:59:58 UTC
[jira] [Commented] (MESOS-6479) add ability to execute batch jobs
from TaskGroupInfo proto in execute.cpp and add string flag for
framework-name
[ https://issues.apache.org/jira/browse/MESOS-6479?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15615950#comment-15615950 ]
Till Toenshoff commented on MESOS-6479:
---------------------------------------
I am retargeting this as 1.1.0 RC2 will be cut soon.
> add ability to execute batch jobs from TaskGroupInfo proto in execute.cpp and add string flag for framework-name
> ----------------------------------------------------------------------------------------------------------------
>
> Key: MESOS-6479
> URL: https://issues.apache.org/jira/browse/MESOS-6479
> Project: Mesos
> Issue Type: Improvement
> Components: cli
> Affects Versions: 1.1.0
> Environment: all
> Reporter: Hubert Asamer
> Priority: Trivial
> Labels: newbie, newbie++, testing
> Original Estimate: 4h
> Remaining Estimate: 4h
>
> Extend execute.cpp to use TaskGroupInfo as container for batch jobs to distribute tasks based on available offers. A simple bool cli flag shall enable/disable such a behavior. If enabled the contents of TaskGroupInfo does not cause the execution of tasks within a "pod" (on a single host) but as distributed jobs (on multiple hosts)
> As an addition an optional cli flag for setting the temporary framework name (e.g. to better distinguish between running/finished frameworks) could be useful.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)