[
https://issues.apache.org/jira/browse/AURORA-1075?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14302869#comment-14302869
]
Dan Mercer commented on AURORA-1075:
------------------------------------
- Perhaps such jobs are expressed without an instance count at all, but with a
flag. Something like 'ubiquitous=True'
- If instances scheduled in this manner are required to run on every slave
(such as a logger, or some other utility service) then they are effectively
immune from preemption.
- Could you elaborate on some of the pitfalls such a feature might introduce in
a multi-framework cluster?
> schedule instance on every host matching constraints
> ----------------------------------------------------
>
> Key: AURORA-1075
> URL: https://issues.apache.org/jira/browse/AURORA-1075
> Project: Aurora
> Issue Type: Story
> Components: Scheduler
> Reporter: Jay Buffington
>
> I'd like aurora to schedule an instance of a given job on every host it has
> seen an offer for. So if I were to create this job:
> {noformat}
> import os
> jobs = [Job(
> task=SimpleTask(name="hello_world", command="echo hello world"),
> role=os.getenv('USER'),
> cluster="cluster1",
> instances="*"
> )]
> {noformat}
> It would result in hello world running on every host in the cluster where
> there is room.
> If I were to set constraints (e.g. dedicated role), only hosts matching
> constraints would have the instances started on it.
> If the Job is a production job, instances of other jobs would be preempted if
> necessary to make room for this instance on every host aurora knows about.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
