Interesting. Thanks Adam.
On Thu, Sep 24, 2015 at 4:17 PM, Adam Bordelon 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 framewo
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.
S
Sorry sorry! In my earlier mail I was referring to Resource Manager.
Let me reformulate my question:
Launch RM using Marathon, it starts as a mesos slave task. In this case
what is the work flow? Does it still register as a framework with
Mesos-Master? is there any document that you can point me
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 <
aharipriy...@
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
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 whic
Haripriya, if you're launching the RM manually, you might choose to launch
it on a Mesos Master (or a slave, or a non-Mesos node), but if you're using
a tool like Marathon to relaunch the RM if it (or its node) fails, then
you'll end up using Mesos to launch the RM itself as a Mesos task, so it
wil
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?
htt
