Marc,

Have you read
https://mesos.readthedocs.io/en/1.1.0/high-availability-framework-guide/ in
particular the section about the FrameworkInfo failover_timeout?

Cheers,

Charles



On Tue, 25 Aug 2020, 16:01 Marc Roos, <m.r...@f1-outsourcing.eu> wrote:

>
>
>
> I assume this was because something happened with zookeeper, and it
> restarted loading the wrong configuration file without the quorum=1.
> Because I was testing with different zookeeper rpms (mesos rpm conf is
> not standard location)
>
> Question: Is this by design that all tasks are terminated when zookeeper
> is gone? Is there some timeout setting that allows tasks to run for a
> day without zookeeper
>
>
>
>
>
> -----Original Message-----
> To: user
> Subject: Suddenly all tasks gone, framework at completed, cannot start
> framework
>
>
>
> Today all my tasks are down and framework marathon is at completed. Any
> idea how this can happen?
>
>
>
> ed.cpp:520] Successfully authenticated with master
> master@192.168.10.151:5050
> I0825 13:03:27.961248   108 sched.cpp:1188] Got error 'Framework has
> been removed'
>
>
>
>

Reply via email to