Return-Path: <user-return-13615-archive-asf-public=cust-asf.ponee.io@storm.apache.org>
X-Original-To: archive-asf-public-internal@cust-asf2.ponee.io
Delivered-To: archive-asf-public-internal@cust-asf2.ponee.io
Received: from cust-asf.ponee.io (cust-asf.ponee.io [163.172.22.183])
	by cust-asf2.ponee.io (Postfix) with ESMTP id 339E7200D40
	for <archive-asf-public-internal@cust-asf2.ponee.io>; Sat, 18 Nov 2017 08:42:51 +0100 (CET)
Received: by cust-asf.ponee.io (Postfix)
	id 320DD160BF7; Sat, 18 Nov 2017 07:42:51 +0000 (UTC)
Delivered-To: archive-asf-public@cust-asf.ponee.io
Received: from mail.apache.org (hermes.apache.org [140.211.11.3])
	by cust-asf.ponee.io (Postfix) with SMTP id 77E88160BE9
	for <archive-asf-public@cust-asf.ponee.io>; Sat, 18 Nov 2017 08:42:50 +0100 (CET)
Received: (qmail 36003 invoked by uid 500); 18 Nov 2017 07:42:48 -0000
Mailing-List: contact user-help@storm.apache.org; run by ezmlm
Precedence: bulk
List-Help: <mailto:user-help@storm.apache.org>
List-Unsubscribe: <mailto:user-unsubscribe@storm.apache.org>
List-Post: <mailto:user@storm.apache.org>
List-Id: <user.storm.apache.org>
Reply-To: user@storm.apache.org
Delivered-To: mailing list user@storm.apache.org
Received: (qmail 35994 invoked by uid 99); 18 Nov 2017 07:42:48 -0000
Received: from mail-relay.apache.org (HELO mail-relay.apache.org) (140.211.11.15)
    by apache.org (qpsmtpd/0.29) with ESMTP; Sat, 18 Nov 2017 07:42:48 +0000
Received: from mail-pg0-f54.google.com (mail-pg0-f54.google.com [74.125.83.54])
	by mail-relay.apache.org (ASF Mail Server at mail-relay.apache.org) with ESMTPSA id 932031A0048
	for <user@storm.apache.org>; Sat, 18 Nov 2017 07:42:48 +0000 (UTC)
Received: by mail-pg0-f54.google.com with SMTP id 4so3640766pge.1
        for <user@storm.apache.org>; Fri, 17 Nov 2017 23:42:48 -0800 (PST)
X-Gm-Message-State: AJaThX5NPPhCWi4fqJZ5Gl6cWfAl2iCFcYrZ6RNphCZ4u8UQAo0NGAuh
	sLUPESKKcSbzJ03S12bTimiUPOo5m1d9Z1lbpY4=
X-Google-Smtp-Source: AGs4zMZ6o2cXYZV/bNMg60TMBp3oi/i2nq0aLjEV7vIkEFC5D/qmTSAlz/7gv8OSDW/4X7wrs+SvjMnpKVQwG8IoSNI=
X-Received: by 10.98.215.19 with SMTP id b19mr4596270pfh.94.1510990967854;
 Fri, 17 Nov 2017 23:42:47 -0800 (PST)
MIME-Version: 1.0
Received: by 10.100.154.139 with HTTP; Fri, 17 Nov 2017 23:42:47 -0800 (PST)
In-Reply-To: <5A0F610302090238003904AB_0_98959@msllnjpmsgsv06>
References: <5A0F610302090238003904AB_0_98959@msllnjpmsgsv06>
From: =?UTF-8?Q?Stig_Rohde_D=C3=B8ssing?= <srdo@apache.org>
Date: Sat, 18 Nov 2017 08:42:47 +0100
X-Gmail-Original-Message-ID: <CAG09ER3yoCmtcR=U4ykQCYw4r6K=9j1Xs0_UhmNg7-TBhfuC-w@mail.gmail.com>
Message-ID: <CAG09ER3yoCmtcR=U4ykQCYw4r6K=9j1Xs0_UhmNg7-TBhfuC-w@mail.gmail.com>
Subject: Re: JVM Tuning in Local Mode
To: user@storm.apache.org
Content-Type: multipart/alternative; boundary="f403045eaf6ce5db7f055e3cff79"
archived-at: Sat, 18 Nov 2017 07:42:51 -0000

--f403045eaf6ce5db7f055e3cff79
Content-Type: text/plain; charset="UTF-8"

As you noted, there is only one process when you run Storm in local mode.
The childopts are only used in cluster mode when new JVMs are spawned (e.g.
supervisor spawning workers). If you need to modify the JVM settings for a
local mode cluster, you can just set the JVM settings for the process you
are starting the LocalCluster from. How you do it will depend on how you
build and run your project.

2017-11-17 23:21 GMT+01:00 Mitchell Rathbun (BLOOMBERG/ 731 LEX) <
mrathbun1@bloomberg.net>:

> I am looking to tune the JVM settings for the Storm instance that we are
> running locally. I know in cluster mode this is done for various nodes by
> using the childopts property in storm.yaml (worker.childopts,
> nimbus.childopts, etc.). What should I set for this to work in local mode?
> Is it necessary for all of these properties to be set even though there is
> only one process that is run? Or is there a simpler way to do it?
>

--f403045eaf6ce5db7f055e3cff79
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">As you noted, there is only one process when you run Storm=
 in local mode. The childopts are only used in cluster mode when new JVMs a=
re spawned (e.g. supervisor spawning workers). If you need to modify the JV=
M settings for a local mode cluster, you can just set the JVM settings for =
the process you are starting the LocalCluster from. How you do it will depe=
nd on how you build and run your project.<br><div class=3D"gmail_extra"><br=
><div class=3D"gmail_quote">2017-11-17 23:21 GMT+01:00 Mitchell Rathbun (BL=
OOMBERG/ 731 LEX) <span dir=3D"ltr">&lt;<a href=3D"mailto:mrathbun1@bloombe=
rg.net" target=3D"_blank">mrathbun1@bloomberg.net</a>&gt;</span>:<br><block=
quote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc=
 solid;padding-left:1ex"><div><div class=3D"m_-3365167672207688452rte-style=
-maintainer" style=3D"font-family:Arial;white-space:pre-wrap;font-size:smal=
l;color:rgb(0,0,0)">I am looking to tune the JVM settings for the Storm ins=
tance that we are running locally. I know in cluster mode this is done for =
various nodes by using the childopts property in storm.yaml (worker.childop=
ts, nimbus.childopts, etc.). What should I set for this to work in local mo=
de? Is it necessary for all of these properties to be set even though there=
 is only one process that is run? Or is there a simpler way to do it?</div>=
</div></blockquote></div><br></div></div>

--f403045eaf6ce5db7f055e3cff79--