David, Keep in mind that there is a scope difference between putting configuration in your code/deployed topology and putting it in storm.yaml on each node: in the former case the parameters will be global for all your topologies whereas in the later case they only apply to one specific topology.
As Patricio correctly mention, it is recommended to use deployment automation tools to ensure conherence of deployed configuration files. Tools like Storm are meant to be used "at scale" => on many hosts => it is assumed that we have some kind of deployment automation system to assist us in the management of that IT landscape. Cheers, S On Tue, Apr 1, 2014 at 12:20 PM, David Crossland <[email protected]>wrote: > That's a pain, thanks. Its either that then or configure it in code... > either way I either have to recompile or touch each node.. > > Still thanks for the info xD > > D > > *From:* Jon Logan <[email protected]> > *Sent:* Tuesday, 1 April 2014 16:43 > *To:* [email protected] > > All nodes. > > > On Tue, Apr 1, 2014 at 11:41 AM, David Crossland <[email protected]>wrote: > >> I'm just wondering about the storm.yaml settings, should these be >> replicated to all nodes in the topology or need it only be configured on >> the "master" node where I deploy the topology? >> >> thanks >> David >> >> >
