[
https://issues.apache.org/jira/browse/AURORA-715?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14137709#comment-14137709
]
Benjamin Mahler commented on AURORA-715:
----------------------------------------
>From our discussions we learned that there were two key things provided by the
>GC Executor:
# Task state reconciliation.
# Sandbox deletion events.
The first will be obviated by the task reconciliation in Mesos. The second is
not solved by task reconciliation. My understanding is that the sandbox
deletion events are only used to gray out links in Aurora's webui, correct?
We discussed the following idea with [~wickman]. In the aurora webui
javascript, lazily use background [JSONP|http://en.wikipedia.org/wiki/JSONP]
requests to the observer(s) to know whether to gray out sandbox links. Since
the user of the UI has to be able to talk to the observer machine:port, the UI
can send [JSONP|http://en.wikipedia.org/wiki/JSONP] requests to the observer(s)
to determine which links need to be grayed out.
We thought of this because there is already a race (up to 1 hour) in which the
link remains clickable but the sandbox is GCed (correct?), and the observer is
the source of truth as to whether it can display information about the task.
How does this sound? Anything that we missed?
> Retire GC Executor
> ------------------
>
> Key: AURORA-715
> URL: https://issues.apache.org/jira/browse/AURORA-715
> Project: Aurora
> Issue Type: Epic
> Reporter: Chris Lambert
>
> Mesos plans to provide a task reconciliation API and sandbox history so that
> we can retire the GC Executor. This Epic captures the work necessary to
> complete this process.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
