Re: High availability feature

2018-04-20 Thread Tomek Janiszewski 
Marathon has its own mechanism. In theory it's similar but differs in
implementation but both rely on Zookeeper (ZK) for leader election. Mesos
uses replica log for keeping data while Marathon stores everything in ZK.

pt., 20.04.2018, 16:06 użytkownik Mahmood Naderan <mahmood...@gmail.com>
napisał:

> Hi,
> I want to know if the high availability feature of mesos is related to
> high availability of Marathon? In other word, mesos supports multiple
> master nodes with an election policy and so on. Does that provide high
> availability feature for marathon? Or marathon has its own mechanism?
>
>
> Regards,
> Mahmood
>

Re: High availability feature

2018-04-20 Thread Ken Sipe 
Marathon provides it’s own HA through multiple instances of Marathon:  
https://mesosphere.github.io/marathon/docs/high-availability.html 
<https://mesosphere.github.io/marathon/docs/high-availability.html>

Ken 

> On Apr 20, 2018, at 9:05 AM, Mahmood Naderan <mahmood...@gmail.com> wrote:
> 
> Hi,
> I want to know if the high availability feature of mesos is related to
> high availability of Marathon? In other word, mesos supports multiple
> master nodes with an election policy and so on. Does that provide high
> availability feature for marathon? Or marathon has its own mechanism?
> 
> 
> Regards,
> Mahmood

High availability feature

2018-04-20 Thread Mahmood Naderan 
Hi,
I want to know if the high availability feature of mesos is related to
high availability of Marathon? In other word, mesos supports multiple
master nodes with an election policy and so on. Does that provide high
availability feature for marathon? Or marathon has its own mechanism?


Regards,
Mahmood