[jira] [Commented] (AURORA-389) provide a mechanism to run a task on every slave

["Bill Farner (JIRA)" <ji...@apache.org>]

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

Bill Farner commented on AURORA-389:
------------------------------------

Thanks for the additional examples!

> provide a mechanism to run a task on every slave
> ------------------------------------------------
>
>                 Key: AURORA-389
>                 URL: https://issues.apache.org/jira/browse/AURORA-389
>             Project: Aurora
>          Issue Type: Task
>          Components: Client, Scheduler
>            Reporter: David Robinson
>            Priority: Minor
>
> Aurora does not provide a mechanism for running a task on every slave. The config for a job requires that the number of instances be specified in advance, but it's not practical to adjust this number whenever slaves are added or removed. If this mechanism were available it could be used to run Thermos Observer or other tasks which need to be run on every slave. Without this mechanism everyone will need to duplicate Aurora's deployment mechanism outside of Aurora. If we could use Aurora to deploy these components we'd avoid this duplication.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)