[
https://issues.apache.org/jira/browse/AURORA-1122?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14320512#comment-14320512
]
Bill Farner commented on AURORA-1122:
-------------------------------------
We might be able to leverage the existing {{getPendingReason}} RPC to expose
this information.
> Show preemption_delay in web ui
> -------------------------------
>
> Key: AURORA-1122
> URL: https://issues.apache.org/jira/browse/AURORA-1122
> Project: Aurora
> Issue Type: Task
> Reporter: Jay Buffington
>
> --preemption_delay (see
> https://github.com/apache/incubator-aurora/blob/master/src/main/java/org/apache/aurora/scheduler/async/preemptor/PreemptorModule.java#L47-L50)
> isn't documented in the user-guide
> https://github.com/apache/incubator-aurora/blob/master/docs/user-guide.md#user-content-giving-priority-to-production-tasks-preempting
> and since it is a system setting the end user has noway of knowing an an
> operator might have set it to.
> Right now when a production job is submitted and the cluster is "full" of
> non-prod jobs the prod job will go into "PENDING" state and the user will see
> a message such as "Insufficient CPU" There is no acknowledgement that the
> job will attempt to preempt non-prod jobs after some operator configured
> amount of time. This is confusing to users.
> I propose when a prod job cannot be immediately scheduled the UI gives the
> user a message that says something to the effect "Will attempt to preempt
> non-production Jobs in ~9m42s"
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
