AFAIK there are no breaking changes only some deprecations/removals. You might want to see changelog and do not skip versions when doing upgrade https://github.com/apache/mesos/blob/master/CHANGELOG#L368
śr., 29 sie 2018 o 02:43 użytkownik Antony A <antonyaugus...@gmail.com> napisał: > Thank you. I will try upgrading marathon. I am also planing to upgrade > mesos1.6. > > Please can you let me know if I have to be aware of any breaking releases > from 1.2 to 1.6? > > Thanks > Antony > > Sent from my mobile. *Please excuse any typos.* > > On Aug 24, 2018, at 10:45 AM, Tomek Janiszewski <jani...@gmail.com> wrote: > > Please attach logs. > You should update to 1.4.12 there were a lot of bugs fixed and there's a > chance you run into one of them > https://github.com/mesosphere/marathon/blob/v1.4.12/changelog.md > > pt., 24 sie 2018, 18:00 użytkownik Harold Dost <haroldd...@gmail.com> > napisał: > >> Are there any indications in the logs? Generally scheduling and >> de-scheduling should show there. >> >> On Fri, Aug 24, 2018, 11:14 Antony A <antonyaugus...@gmail.com> wrote: >> >>> I am relative new to Mesos/Marathon. In my marathon framework I noticed >>> recently couple of times all the applications got deleted. I had to >>> redeploy from my artifact to get the application available again.Has anyone >>> noticed the same. Any pointers on where to look for errors/changes? >>> >>> >>> Here are the version of mesos and marathon. >>> >>> mesos 1.2.0 (5 node master and 5 node zk) running on the 5 VMs. >>> mesos 1.3.0 (agent) >>> marathon-1.4.3 >>> >>> Thanks >>> AAA >>> >>>
