I've gotten a little farther on this issue by increasing the mesos slave memory to 4 GB from 2GB. The node manager task get launched and sits in the STAGING state for a minute and then the mesos-slave.INFO log shows:
I0115 15:19:12.114537 30903 slave.cpp:3841] Terminating executor myriad_executor20160115-145750-344821002-5050-30838-000020160115-145750-344821002-5050-30838-O18020160115-145750-344821002-5050-30838-S0 of framework 20160115-145750-344821002-5050-30838-0000 because it did not register within 1mins I then increased the mesos slave's executor_registration_timeout setting from 1mins to 5mins to see if that would make a difference but still get the following in the log: I0115 15:19:12.114537 30903 slave.cpp:3841] Terminating executor myriad_executor20160115-145750-344821002-5050-30838-000020160115-145750-344821002-5050-30838-O18020160115-145750-344821002-5050-30838-S0 of framework 20160115-145750-344821002-5050-30838-0000 because it did not register within 5mins Is there any guidance on why the Myriad executor fails to register with the Mesos slave? Thanks, Matt -----Original Message----- From: Matthew J. Loppatto Sent: Thursday, January 14, 2016 2:25 PM To: '[email protected]' Subject: RE: Myriad Vagrant Setup Issue Sarjeet, Thanks for the reply. I modified the medium profile in my myriad-config-default.yml file to use 1 cpu and 1024 MB mem and am seeing a similar issue in the YARN resource manager log: Offer not sufficient for task with, cpu: 1.4, memory: 2432.0, ports: 1001 If I try lowering the medium profile memory below 1024 I get the following message in the log: NodeManager from vagrant-ubuntu-trusty-64 doesn’t satisfy minimum allocations, Sending SHUTDOWN signal to NodeManager. Increasing the memory of the VM to 6 GB also didn't solve the issue. Are there any other measures I can take to resolve the insufficient resource messages? Thanks, Matt -----Original Message----- From: sarjeet singh [mailto:[email protected]] Sent: Thursday, January 14, 2016 12:41 PM To: [email protected] Subject: Re: Myriad Vagrant Setup Issue Matthew, You can modify profile configurations for Nodemanagers in myriad-config-default.yml and reduce medium (default) NM configuration to match with your VM capacity so a default NM (medium profile) could launch without any issue. - Sarjeet Singh On Thu, Jan 14, 2016 at 10:56 PM, Matthew J. Loppatto < [email protected]> wrote: > Hi, > > I'm trying to setup Myriad for an R&D project at my company but I'm > having some trouble even getting the Vagrant VM working properly. I > followed the instructions here: > > https://github.com/apache/incubator-myriad/blob/master/docs/vagrant.md > > with some minor corrections but the Node Manager fails to start. It > looks like a resource issue based on the log output. The Mesos UI > shows a slave process with 2 cpu and 2 GB mem, but the log states the > task requires 4 cpu and 5.5 GB mem. > > I've detailed my configuration and log output in this public Gist: > > https://gist.github.com/FearTheParrot/626259c23a854645fcbf > > Would it be possible to provision the Mesos slave with more resources > while also reducing the profile size of the Node Manager? The Vagrant > VM only has 4 GB ram and 2 cpu. > > Any help would be appreciated. > > Thanks! > Matt >
