. I'd
be interested in your findings!
On Tue, Dec 12, 2017 at 4:32 PM, Mohit Jaggi <mohit.ja...@uber.com> wrote:
> For the same position I see two bursts of writes, one around 00:12:36 and
> another 12 min earlier. Any idea what this means?
>
> ~/a/a/aurora-outage ❯❯❯ grep 6751
gt; having some issues) during that time?
>
> On Wed, Dec 13, 2017 at 9:27 AM, Mohit Jaggi <mohit.ja...@uber.com> wrote:
>
>> Folks,
>> Can you help please?
>>
>> Mohit.
>> -- Forwarded message --
>> From: Bill Farner <wfar...@ap
g this window would help, it looks like an
> agent termination is involved here as well?
>
> On Fri, Oct 27, 2017 at 3:09 PM, Mohit Jaggi <mohit.ja...@uber.com> wrote:
>
>> Here are some relevant logs. Aurora scheduler logs shows the task going
>> from:
>> INIT
>>
r. +jie,gilbert, is there a CLI command for 'exec'ing into the
> container?
>
> On Tue, Oct 31, 2017 at 12:47 PM, Mohit Jaggi <mohit.ja...@uber.com>
> wrote:
>
>> Yes. There is a fix available now in Aurora/Thermos to try and exit in
>> such scenarios. But I am curious
e
> framework (Aurora) knows this expected behavior of Thermos and can clean up
> ones that get stuck after the task terminates. However, we currently don't
> provide a great executor lifecycle API to enable schedulers to do this
> (it's long overdue).
>
> On Tue, Oct 31, 2017 at 2:4
y, due to the answer I provided: there
> isn't a complete lifecycle API for the executor. (This includes
> healthiness, state updates, reconciliation, ability for scheduler to shut
> it down, etc).
>
> On Tue, Oct 31, 2017 at 4:27 PM, Mohit Jaggi <mohit.ja...@uber.com> wrote:
Folks,
Often I see some orphaned executors in my cluster. These are cases where
the framework was informed of task loss, so has forgotten about them as
expected, but the container(docker) is still around. AFAIK, Mesos agent is
the only entity that has knowledge of these containers. How do I ensure
w thread
On Fri, Oct 27, 2017 at 2:25 PM, Vinod Kone <vinodk...@apache.org> wrote:
> Can you share the agent and executor logs of an example orphaned executor?
> That would help us diagnose the issue.
>
> On Fri, Oct 27, 2017 at 8:19 PM, Mohit Jaggi <mohit.ja...@uber.com>
Folks,
I am trying to change Apache Aurora's code to call SHUTDOWN instead of
KILL. However, it seems that the SchedulerDriver class in Mesos does not
have a shutdownExecutor() call.
t; That's right. It is only available for v1 schedulers.
>
> On Fri, Jan 5, 2018 at 3:38 PM, Mohit Jaggi <mohit.ja...@uber.com> wrote:
>
>> Folks,
>> I am trying to change Apache Aurora's code to call SHUTDOWN instead of
>> KILL. However, it seems that the Sched
e Shutdown call will work with that default executor.)
>>
>> On Tue, Jan 16, 2018 at 4:49 PM, Mohit Jaggi <mohit.ja...@uber.com>
>> wrote:
>>
>>> Gotcha. Another question: if a framework doesn't use executors, can it
>>> still use the SHUTDOWN call?
>>
.
>
> -anand
>
> On Fri, Jan 12, 2018 at 3:28 PM, Mohit Jaggi <mohit.ja...@uber.com> wrote:
>
>> Are you suggesting
>>
>> *send(new Call(METHOD, Param1, ...)) *
>>
>> instead of
>>
>> *driver.method(Param1, )*
>>
>> *
g you
> to send the 'SHUTDOWN' call. We also have a V0Mesos class that uses the old
> scheduler driver internally.
>
> -anand
>
> On Wed, Jan 10, 2018 at 2:53 PM, Mohit Jaggi <mohit.ja...@uber.com> wrote:
>
>> Thanks Vinod. Is there a V1SchedulerDriver.java fil
13 matches
Mail list logo
