Answers inline.

Regards,
Richards Peter.

On Tue, Sep 23, 2014 at 8:55 PM, Gunderson, Richard-CW <
richard.gunder...@bestbuy.com> wrote:

>  Hi Storm users.
>
>
>
> I’ve recently started managing a Storm cluster. I’m very new to Storm and
> have a lot to learn. I’ve been tasked to create Chef scripts to automate
> two things:
>
> 1)      Update our storm cluster if we have changes to our Storm
> configuration (this will primarily be changes to properties in the
> storm.yaml file)
>
> 2)      Updates to our topologies.
>
>
>
> My question: Does storm notice if the properties file (storm.yaml, or
> cluster.xml) has been updated and automatically “incorporate” the changes
> while it’s running? Or must I shut down the entire cluster (*nimbus and
> all supervisors*) and restart everything? I didn’t notice anywhere in the
> official apache storm documentation about what to do when after updating
> the configuration file.
>
>
>

>From my experience, storm.yaml file is read only once - when storm
daemons(nimbus, supervisor, ui) are started. If you are adding only new
supervisors machines into the cluster you need not restart any of the
running services. You just have to start the supervisor on the newly added
machine. In storm.yaml file you do not specify the ip address of any of the
supervisor machines. The supervisors automatically talk to the nimbus
server configured in the storm.yaml file. Storm is stateless and all state
information is stored in zookeeper. So you need not worry about adding any
new supervisor machines.

I normally restart all the storm daemons if there is a change in my
storm.yaml file. You should take expert opinion from others in this forum.

But let me bring one more thing to your attention. If you add more
supervisor ports in your storm yaml file, you should also increase a
configuration parameter in zoo.cfg file of zookeeper -> maxClientCnxns.
http://zookeeper.apache.org/doc/r3.3.3/zookeeperAdmin.html#sc_advancedConfiguration



>  Also: What happens if Nimbus has a different storm.yaml file than the
> supervisors? Does a supervisor process ever read that file? Or does Nimbus
> control everything?
>

I am not sure about your question. If the nimbus machine runs only nimbus,
then that file is read only by nimbus. However if you have nimbus and
supervisor running on same machine the file will be read by both the
processes.

>
>
> We have recently created two new topologies and will need to start tuning
> the performance of these topologies, so we’ll have a lot of need to update
> our configuration a lot in the coming days.
>
>
>
> Thank you,
>
>
>
> Richard Gunderson
>

Reply via email to