Mesos slave ID change after reboot

2018-01-10 Thread Srikanth Viswanathan
I am trying to understand under what cases the mesos slave ID changes in response to reboot. I noticed this note at http://mesos.apache.org/documentation/latest/upgrades/#upgrading-from-1-3-x-to-1-4-x : Agent is now allowed to recover its agent ID post a host reboot. This > prevents the

New 1.5 Marathon deb package - no documentation

2018-01-10 Thread Adam Cecile
Hello, I'm testing Mesos 1.4 + marathon 1.5 update but I cannot understand how marathon 1.5 deb package works. Marathon binary seems to completely ignore my /etc/marathon/* config files used by previous version and when looking at the systemd file, I do not understand how to pass startup

Re: New 1.5 Marathon deb package - no documentation

2018-01-10 Thread haosdent
marathon 1.5 use /usr/share/marathon/conf/application.ini as configure file. On Wed, Jan 10, 2018 at 4:59 PM, Adam Cecile wrote: > Hello, > > > I'm testing Mesos 1.4 + marathon 1.5 update but I cannot understand how > marathon 1.5 deb package works. > > Marathon binary

Re: New 1.5 Marathon deb package - no documentation

2018-01-10 Thread Adam Cecile
Uh ? It's not even provided in the package: root@dev:~# dpkg -L marathon | grep ini root@dev:~# On 01/10/2018 10:01 AM, haosdent wrote: marathon 1.5 useĀ /usr/share/marathon/conf/application.ini as configure file. On Wed, Jan 10, 2018 at 4:59 PM, Adam Cecile

Re: Mesos rare TASK_LOST scenario v 0.21.0

2018-01-10 Thread Ajay V
Thanks for getting back Vinod. So, does that mean that even for v1.2, these race conditions (where the command executor doesn't stay long enough ) existed and that 1.3 versions fixes them ?. Reason for asking is because I did try an upgrade to v1.2 and still found very similar issues. Regards,

Re: Mesos rare TASK_LOST scenario v 0.21.0

2018-01-10 Thread Vinod Kone
The command executor was probably fixed somewhere between 0.21 and 1.3. The only reason I mentioned 1.3+ is because any releases before that are out of support period. If you can repro the issue with 1.3+ and paste the logs here or in a JIRA, we can help debug it for you. On Wed, Jan 10, 2018 at

Re: Mesos replicated log fills disk with logging output

2018-01-10 Thread Stephan Erb
Thanks for the hint! The cluster is using ext4, and judging from the linked thread this could have indeed be caused by a stalling hypervisor. From: Jie Yu Reply-To: "user@mesos.apache.org" Date: Monday, 8. January 2018 at 23:36 To: user

Re: java driver/shutdown call

2018-01-10 Thread Mohit Jaggi
Thanks Vinod. Is there a V1SchedulerDriver.java file? I see https://github.com/apache/mesos/tree/72752fc6deb8ebcbfbd5448dc599ef3774339d31/src/java/src/org/apache/mesos/v1/scheduler but it does not have a V1 driver. On Fri, Jan 5, 2018 at 3:59 PM, Vinod Kone wrote: > That's