[
https://issues.apache.org/jira/browse/AURORA-160?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Bill Farner resolved AURORA-160.
--------------------------------
Resolution: Won't Fix
Given the amount of effort required to do this and the goal to sunset the GC
executor, i propose we don't do this.
> implement the ability to do one-off GC executor runs
> ----------------------------------------------------
>
> Key: AURORA-160
> URL: https://issues.apache.org/jira/browse/AURORA-160
> Project: Aurora
> Issue Type: Task
> Components: Client, Scheduler
> Reporter: brian wickman
> Priority: Minor
>
> 1) add a read-only admin endpoint that (when given a hostname) gives the
> AdjustRetainedTask message for that machine.
> 2) add a standalone executable that queries the scheduler and runs a GC.
> Right now there is nothing that prevents us from oversubscribing a machine to
> the point that we can no longer schedule GC executors, so we should have the
> ability to do one-off runs either outside of the scheduler or give GC
> executors some preemption priority over non-production tasks.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
