Return-Path: X-Original-To: apmail-storm-user-archive@minotaur.apache.org Delivered-To: apmail-storm-user-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id AD7D5109F7 for ; Tue, 1 Apr 2014 16:49:09 +0000 (UTC) Received: (qmail 69017 invoked by uid 500); 1 Apr 2014 16:49:09 -0000 Delivered-To: apmail-storm-user-archive@storm.apache.org Received: (qmail 68983 invoked by uid 500); 1 Apr 2014 16:49:07 -0000 Mailing-List: contact user-help@storm.incubator.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: user@storm.incubator.apache.org Delivered-To: mailing list user@storm.incubator.apache.org Received: (qmail 68974 invoked by uid 99); 1 Apr 2014 16:49:06 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 01 Apr 2014 16:49:06 +0000 X-ASF-Spam-Status: No, hits=1.8 required=5.0 tests=HTML_FONT_FACE_BAD,HTML_MESSAGE,RCVD_IN_DNSWL_LOW,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of svend.vanderveken@gmail.com designates 209.85.216.48 as permitted sender) Received: from [209.85.216.48] (HELO mail-qa0-f48.google.com) (209.85.216.48) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 01 Apr 2014 16:49:02 +0000 Received: by mail-qa0-f48.google.com with SMTP id m5so9745773qaj.7 for ; Tue, 01 Apr 2014 09:48:42 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; bh=KJlMxJk5L2Jex0dDWnqACExTHebUWEsrXsjxN0QAjLU=; b=EpzX5dg/FhToZP7nWYS76KRfnlGeq3YuLS1OKWPh3sQT/zv/PZ6ZCCiIpD75+1faS2 quRA80bAa0ywOqM3pgcNDBea1JT134/5a+QNZszTxhnf5g/RNTQCWCWIWsh6lkCA7jnt yMhSv1LpVJ3YSHmpLz7sZNwUpkP2Fbd7CRlvBnsbaqYzTB06CDEG8+qrPtAbvPJVgztB t77wvl03VA2CNvuTd2AbMaOhwZsI0XLTejgaHj9HevffHGlaq2eczJse13fkHOZ8wr/m ZWYk7qqF9lZE7esJ2gq22sN1+JXAFVEmsk1abSb01PqPOECZhSM6PcY1tPnr9EnLONhP wHow== MIME-Version: 1.0 X-Received: by 10.140.104.228 with SMTP id a91mr3287649qgf.113.1396370921962; Tue, 01 Apr 2014 09:48:41 -0700 (PDT) Received: by 10.140.44.74 with HTTP; Tue, 1 Apr 2014 09:48:41 -0700 (PDT) In-Reply-To: <596e4eb0aa5e41ceb33aa846871cbecb@DBXPR07MB398.eurprd07.prod.outlook.com> References: <596e4eb0aa5e41ceb33aa846871cbecb@DBXPR07MB398.eurprd07.prod.outlook.com> Date: Tue, 1 Apr 2014 12:48:41 -0400 Message-ID: Subject: Re: Curiosity From: Svend Vanderveken To: user@storm.incubator.apache.org Content-Type: multipart/alternative; boundary=001a11354186c741d204f5fdf0cb X-Virus-Checked: Checked by ClamAV on apache.org --001a11354186c741d204f5fdf0cb Content-Type: text/plain; charset=ISO-8859-1 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 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 > *Sent:* Tuesday, 1 April 2014 16:43 > *To:* user@storm.incubator.apache.org > > All nodes. > > > On Tue, Apr 1, 2014 at 11:41 AM, David Crossland 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 >> >> > --001a11354186c741d204f5fdf0cb Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable
David, 

Keep in mind that there is= a scope difference between putting configuration in your code/deployed top= ology and putting it in storm.yaml on each node: in the former case the par= ameters will be global for all your topologies whereas in the later case th= ey 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" =3D> = on many hosts =3D> it is assumed that we have some kind of deployment au= tomation system to assist us in the management of that IT landscape. <= /div>

Cheers, 

S


On Tue, Apr 1, 2= 014 at 12:20 PM, David Crossland <david@elastacloud.com>= 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..<= /div>

Still thanks for the info xD

D

From:&= nbsp;Jon Logan
Sent: Tuesday, 1 April 2014 16:43
To: user@storm.incubator.apache.org

All nodes.


On Tue, Apr 1, 2014 at 11:41 AM, David Crossland= <david@elasta= cloud.com> 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 th= e “master” node where I deploy the topology?

thanks
David



--001a11354186c741d204f5fdf0cb--