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 promoted to to primary, and Marathon will launch a new instance to replace the replica.
There are more details in https://www.joyent.com/blog/dbaas-simplicity-no-lock-in --Casey > On May 12, 2016, at 2:56 AM, <suruchi.kum...@accenture.com> > <suruchi.kum...@accenture.com> wrote: > > 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 UI and > try on of its instance to kill. Will the information saved in the database > will be remain in the new one replacing it. > > > Thanks > > > > > > > This message is for the designated recipient only and may contain privileged, > proprietary, or otherwise confidential information. If you have received it > in error, please notify the sender immediately and delete the original. Any > other use of the e-mail by you is prohibited. Where allowed by local law, > electronic communications with Accenture and its affiliates, including e-mail > and instant messaging (including content), may be scanned by our systems for > the purposes of information security and assessment of internal compliance > with Accenture policy. > ______________________________________________________________________________________ > > www.accenture.com
