15/06/19 17:12:10 INFO scheduler.MyriadOperations: Will skip flexing down 2 Node Manager instances that were launched but have not yet registered with Resource Manager.
This is an interesting line. Did you see the nodes in the resource mangers ui? On Fri, Jun 19, 2015 at 1:44 PM, Donald Hansen <[email protected]> wrote: > Thanks for the reply. > > I called FlexUp twice and I see 2 Active Tasks in the Myriad UI as well as > the Mesos UI. After calling FlexUp, I waited a few minutes and then tried > FlexDown. I didn't try to run anything though. > > > On Fri, Jun 19, 2015 at 10:41 AM, yuliya Feldman < > [email protected]> wrote: > > > Great to hear you are trying Myriad. > > When you did flexup - did any of NMs started based on that call and you > > were able to run some jobs?Seems like you can not flex down since "flexed > > up" NMs are not registered back with RM > > From: Donald Hansen <[email protected]> > > To: [email protected] > > Sent: Friday, June 19, 2015 10:26 AM > > Subject: flexdown / not registered with resource manager > > > > I'm new to Myriad and not sure if this is the right place to post this. > Let > > me know if it isn't. > > > > I'm doing a POC to try and get Myriad integrated into Ambari. I got it > all > > working somewhat and am able to send a FlexUp from my Ambari UI. When I > do > > a FlexDown, I get this error: > > > > 15/06/19 17:12:10 INFO scheduler.MyriadOperations: About to flex down 1 > > instances > > 15/06/19 17:12:10 INFO scheduler.MyriadOperations: Will skip flexing > down 2 > > Node Manager instances that were launched but have not yet registered > with > > Resource Manager. > > 15/06/19 17:12:10 INFO scheduler.MyriadOperations: Flexed down 0 of 1 > > instances including 0 staging instances, and 0 pending instances. > > > > I also get this when calling the API directly as well as when using the > > Myriad UI. > > > > Any ideas? > > > > Thanks. > > Donald > > > > > > > > >
