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 ( https://mesosphere.com/blog/2016/05/04/emc-external-storage-stateful-services/) that showcases how you could bring up a new instance with the same data present, even if its on a different node.
On Thu, May 12, 2016 at 5:59 AM <suruchi.kum...@accenture.com> wrote: > > > 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 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 >
