Interesting. Thanks Adam. On Thu, Sep 24, 2015 at 4:17 PM, Adam Bordelon <[email protected]> wrote:
> Haripriya, the RM (and Myriad scheduler) run as a Mesos task, and as a part > of that task, the Myriad scheduler sends a RegisterFrameworkMessage to the > Mesos master, asking Mesos to register a new Myriad framework and > communicate with this scheduler process for resource offers and status > updates. > > So you ask Marathon to launch an app with 1 instance of the > RM/MyriadScheduler, and then that runs as a Mesos/Marathon task, and it > registers with Mesos as a new framework scheduler, after which point Mesos > starts making resource offers to the MyriadScheduler (as well as Marathon), > and the MyriadScheduler uses its offers to launch NMs. > > The slightly tricky/confusing part is that the Myriad scheduler process' > resources are accounted for under the Marathon framework that launched it, > not as a part of the Myriad framework itself. Only tasks launched by the > Myriad scheduler (i.e. NodeManagers) are accounted for under the Myriad > framework's share of resources. > > On Thu, Sep 24, 2015 at 3:59 PM, Aashreya Shankar <[email protected]> > wrote: > > > Hi, > > > > With Myriad we do not launch Node Manager using Marathon. > > We launch ResourceManager from Marathon. > > Now Myriad takes care of launching more NodeManagers on Mesos slaves as > it > > gets flex up requests. > > > > Thank you > > Aashreya > > > > > > On Thu, Sep 24, 2015 at 3:54 PM, Haripriya Ayyalasomayajula < > > [email protected]> wrote: > > > > > Thanks. > > > > > > So when we use marathon to launch node manager - it starts as a mesos > > slave > > > task. In this case how can it register as a framework with > Mesos-Master? > > is > > > there any document that you can point me to - I'm trying to understand > > the > > > workflow better in this case? > > > > > > On Thu, Sep 24, 2015 at 12:56 PM, Swapnil Daingade < > > > [email protected]> wrote: > > > > > > > RM is just another Mesos task if launched using something like > > Marathon. > > > RM > > > > in turn will register with Mesos as another framework. > > > > You will need mesos slave to launch a mesos task. The RM mesos task > can > > > get > > > > launched on any node having a Mesos slave. > > > > > > > > You can technically launch a RM on any node which has the right > > binaries > > > > and config files from the cli > > > > but then resources consumed by RM will not be accounted for by Mesos. > > > Also > > > > you will not have access > > > > to features like HA. > > > > > > > > Regards > > > > Swapnil > > > > > > > > > > > > > > > > On Thu, Sep 24, 2015 at 12:21 PM, Haripriya Ayyalasomayajula < > > > > [email protected]> wrote: > > > > > > > > > Hi, > > > > > > > > > > My understanding was that the Yarn Resource manager will run > > alongside > > > > > Mesos Master (In practise I was starting a resource manager on a > node > > > > with > > > > > Mesos master running and no mesos slave process) but I see that the > > RM > > > is > > > > > running on a node which is a mesos slave - can anyone please > clarify? > > > > > > > > > > > > > > > > > > > > > > > > > http://events.linuxfoundation.org/sites/events/files/slides/Apache_Myriad_MesosCon_2015.pdf > > > > > (slide 24) > > > > > > > > > > -- > > > > > Regards, > > > > > Haripriya Ayyalasomayajula > > > > > > > > > > > > > > > > > > > > > -- > > > Regards, > > > Haripriya Ayyalasomayajula > > > > > > -- Regards, Haripriya Ayyalasomayajula
