aurora-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Bill Farner (JIRA)" <j...@apache.org>
Subject [jira] [Resolved] (AURORA-1112) support a cluster service job priority
Date Fri, 06 Feb 2015 23:46:36 GMT

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

Bill Farner resolved AURORA-1112.
---------------------------------
    Resolution: Duplicate

> support a cluster service job priority 
> ---------------------------------------
>
>                 Key: AURORA-1112
>                 URL: https://issues.apache.org/jira/browse/AURORA-1112
>             Project: Aurora
>          Issue Type: Story
>          Components: Scheduler
>            Reporter: Jay Buffington
>
> I propose we support a "cluster service" (I'm open to alternative names) priority level
which is higher than production.  Jobs in this priority would be able to preempt production
jobs and would not be subject to quota.  Only a very small set of cluster administrators would
be able to start jobs at this priority level.
> Thermos observer in it's current incarnation is the best example of something that would
run at this priority.  We currently accomplish guaranteeing that the observer is running by
starting it out of band of mesos.  With this change we would be able to start an observer
on a slave through aurora, even if that particular slave is "full" of production tasks.
> There are other examples of cluster services, such as a splunk forwarder, or the mesos-slave
process (eek! turtles!)



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

Mime
View raw message