storm-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From David Crossland <da...@elastacloud.com>
Subject Re: storm.yml conflict, which one to use?
Date Tue, 08 Apr 2014 14:41:10 GMT
In that sense then fair enough, as you are only running UI in one location you probably need
only configure that parameter on that node.

You mentioned worker.childopts, I assume you have a worker on the same node as nimbus then?
Even so I would expect this value to be consistent across all nodes.

But tbh, you might as well duplicate the same yaml to all nodes, the node will ignore any
parameters it doesn't need.  And the values it does use will be consistent across all nodes.

Again I reiterate I probably don't have a clue what I'm talking about.  To make my life simpler
I just duplicated the yaml file to all nodes.  This stopped me having to manage multiple versions.
 I like to make things easy for myself where possible.....
D

From: howard chen<mailto:howachen@gmail.com>
Sent: ?Tuesday?, ?8? ?April? ?2014 ?15?:?12
To: user@storm.incubator.apache.org<mailto:user@storm.incubator.apache.org>

Hi

Because it does not make sense to duplicate, for example, ui.childopts
in supervisor'storm.yaml right?

So I want to know how the storm.yaml is being used, so I can remove
these duplicates if they are really dummy and not used.

On Tue, Apr 8, 2014 at 9:38 PM, David Crossland <david@elastacloud.com> wrote:
> To my (rather limited) knowledge storm.yaml should be consistent across all
> locations. It can be overridden in your topology jar.
>
> D
>
> From: howard chen
> Sent: Tuesday, 8 April 2014 14:28
> To: user@storm.incubator.apache.org
>
> Hi,
>
> I deployed storm into different machines
>
> a. nimbus
> b. ui
> c. supervisor
>
> Let say I want to set the "worker.childopts", if my value of this
> setting in the nimbus' storm.yml and supervisor storm.yml are
> different, which value will storm cluster use?
>
> I ask this because I have seen that in the storm ui, it is showing the
> nimbus value instead of the supervisor value, which is quite
> unexpected.

Mime
View raw message