On Tue, Apr 29, 2014 at 08:51:19AM +0800, Chengwei Yang wrote:
> On Mon, Apr 28, 2014 at 04:15:25PM +0200, Tomas Barton wrote:
> > Hi Chengwei,
> > 
> > 
> > | 1. Is it necessary to deploy storm nimbus on the mesos master node?
> > 
> > Yes, basically Nimbus runs as Mesos framework (inside Mesos master), if 
> > Mesos
> > master dies, it should start automatically on a different node.
> > It's not a standard Nimbus, it's MesosNimbus (Mesos framework):
> > code might look this (it's slightly outdated version):
> > https://github.com/nathanmarz/storm-mesos/blob/master/src/jvm/storm/mesos/
> > MesosNimbus.java
> 
> Thanks!
> 
> > 
> > 
> > | 2. How to deploy storm supervisor node?
> > 
> > No need to do that. MesosNimbus will find resources and will run supervisor
> > process when a topology is submitted.
> 
> Thank you, I saw that mesos.executor.uri set to the storm-mesos tarball,
> however, my VM can not access external network, so I'll verify that by
> setup a internal http server.

This is confirmed, yes, supervisor started on-deman by storm-mesos.

When I exploring storm-mesos, I found some more questions.

I started storm-starter-0.0.1-SNAPSHOT.jar as a storm topology just like
the guide http://mesosphere.io/learn/run-storm-on-mesos/#step-9

And I do saw that topology start to run with only 1 supervsior, 1 worker.
However, I found something, maybe bugs, confused me.

1. The storm UI says the only supervsior provides *0* slots, why not the
default 4? I think below command says correctly, so this is a
storm-mesos bug?
  # ./bin/storm remoteconfvalue supervisor.slots.ports
  supervisor.slots.ports: [6700 6701 6702 6703]

2. As question 1, the default ports are [6700 6701 6702 6703]. However,
the started worker, the process name, says -Dworker.port=31000 in its
command line and the netstat also confirmed that. I see [31000-32000]
are DEFAULT_PORTS in mesos. I suspect this is used as -Dworker.port? Why
not one of [6700 6701 6702 6703]?

3. Even storm-mesos framework get killed, it still displayed as
*activate framework* in mesos web ui. I wait for several minutes and
didn't see any change.

--
Thanks,
Chengwei

> 
> --
> Thanks,
> Chengwei
> > 
> > Tomas
> > 
> > On 28 April 2014 03:49, Chengwei Yang <[email protected]> wrote:
> > 
> >     Hi List,
> > 
> >     I found mesosphere has a good page
> >     http://mesosphere.io/learn/run-storm-on-mesos/ to guide user setup a
> >     mesos-storm cluster.
> > 
> >     However, I found myself several questions about that guide.
> > 
> >     1. Is it necessary to deploy storm nimbus on the mesos master node?
> > 
> >     The guide only says about deploy storm nimbus on the mesos master node.
> > 
> >     But I think it's fine to deploy storm nimbus on a different node. Am I
> >     right?
> > 
> >     2. How to deploy storm supervisor node?
> > 
> >     The guide doesn't say anything about deploy supervisor node, from that
> >     guide, I see superviosr node deploy on-demand when a topology submitted?
> >     Does mesos-storm do such cool stuff?
> > 
> >     If not, we need deploy supervisor in all mesos nodes?
> > 
> >     --
> >     Thanks,
> >     Chengwei
> > 
> > 

Reply via email to