>> https://github.com/emccode
>>
>> blog.emccode.com
>>
>>
>>
>> @cantbewong
>>
>>
>>
>> From: suruchi.kum...@accenture.com [mailto:suruchi.kum...@accenture.com]
>> Sent: Thursday, May 12, 2016 2:59 AM
code.com>*
>
>
>
> @cantbewong
>
>
>
> *From:* suruchi.kum...@accenture.com [mailto:suruchi.kum...@accenture.com]
>
> *Sent:* Thursday, May 12, 2016 2:59 AM
> *To:* user@mesos.apache.org
> *Subject:* Deploying MySQL and WordPress Docker Containers through
]
Sent: Thursday, May 12, 2016 2:59 AM
To: user@mesos.apache.org
Subject: Deploying MySQL and WordPress Docker Containers through Marathon
Hi ,
In case we are killing one of the instances running through Marathon UI. It is
able to bring up another replacing it.
So, would like to know
The MySQL service automatically clusters with a single primary and any number
of replicas. If a replica fails, Marathon will replace it, and the new instance
will automatically bootstrap itself with a copy of the DB and join the cluster.
If the primary should fail, one of the replicas will be
You can do it either way actually. The default case is for it to bring up
a fresh instance of MySQL, since the sandbox the application starts in is
clean. Mesosphere had a recent blog post about using persistent storage in
Marathon (
Hi ,
In case we are killing one of the instances running through Marathon UI. It is
able to bring up another replacing it.
So, would like to know is it a replication of the previous instance which was
killed or it's a new one.
For example, if we are running a MySQL application through
Hi ,
In case we are killing one the instances running through Marathon UI. It is
able to bring up another replacing it.
So, would like to know is it a replication of the previous instance which was
killed or it's a new one.
For example, if we are running a MySQL application through Marathon
7 matches
Mail list logo
