When you run those commands you are not submitting the topology to a Storm
cluster. You are running the topology in local mode, where Storm simulates
a cluster by running the supervisors, workers and Nimbus in a single JVM.
In your case this JVM is started by Maven. As a result the
topology.worker.childopts setting has no effect, because there are no child
processes to pass parameters to, since the workers are just running as
threads in the single JVM. Normally when you submit a topology to a
distributed mode Storm cluster and a supervisor process decides to start
workers, those workers run in their own JVMs.

If you want to set JVM options for the local mode cluster, you should look
up how to set xmx for Maven when using java:exec. Here's a stackoverflow
thread about it https://stackoverflow.com/questions/21468425/mvn-javaexec-
with-increased-memory.

I don't understand what you are referring to when you say the result file
is 50KB. Which result file?

2017-07-27 0:59 GMT+02:00 sam mohel <sammoh...@gmail.com>:

> I submit my topology by this command
> mvn package
> mvn compile exec:java -Dexec.classpathScope=compile
> -Dexec.mainClass=trident.Topology
>   and i copied those lines
> 11915 [Thread-47-b-4] INFO  b.s.d.executor - Prepared bolt b-4:(40)
> 11912 [Thread-111-b-2] INFO  b.s.d.executor - Prepared bolt b-2:(14)
> 11934 [Thread-103-b-5] INFO  b.s.d.executor - Prepared bolt b-5:(45)
> sam@lenovo:~/first-topology$
>
> from what i saw in terminal . I checked the size of the result file and
> found it's 50 KB each time i submit it .
>
> what should i check ?
>
> On Wed, Jul 26, 2017 at 9:05 PM, Bobby Evans <ev...@yahoo-inc.com> wrote:
>
>> Local mode is totally separate and there are no processes launched except
>> the original one.  Those values are ignored in local mode.
>>
>>
>> - Bobby
>>
>>
>>
>> On Wednesday, July 26, 2017, 2:01:52 PM CDT, sam mohel <
>> sammoh...@gmail.com> wrote:
>>
>>
>> Thanks so much for replying , i tried to submit topology in local mode
>> ... i increased size of worker like
>> conf.put(Config.TOPOLOGY_WORKER_CHILDOPTS,"-Xmx4096m" );
>>
>> but got in terminal
>> 11920 [Thread-121-b-4] INFO  b.s.d.executor - Preparing bolt b-4:(25)
>> 11935 [Thread-121-b-4] INFO  b.s.d.executor - Prepared bolt b-4:(25)
>> 11920 [Thread-67-b-5] INFO  b.s.d.executor - Preparing bolt b-5:(48)
>> 11936 [Thread-67-b-5] INFO  b.s.d.executor - Prepared bolt b-5:(48)
>> 11919 [Thread-105-b-2] INFO  b.s.d.executor - Prepared bolt b-2:(10)
>> 11915 [Thread-47-b-4] INFO  b.s.d.executor - Prepared bolt b-4:(40)
>> 11912 [Thread-111-b-2] INFO  b.s.d.executor - Prepared bolt b-2:(14)
>> 11934 [Thread-103-b-5] INFO  b.s.d.executor - Prepared bolt b-5:(45)
>> sam@lenovo:~/first-topology$
>>
>> and didn't complete processing . the size of the result is 50 KB . This
>> topology was working well without any problems . But when i tried to submit
>> it now , i didn't get the full result
>>
>>
>> On Wed, Jul 26, 2017 at 8:35 PM, Bobby Evans <ev...@yahoo-inc.com> wrote:
>>
>> worker.childops is the default value that is set by the system
>> administrator in storm.yaml on each of the supervisor nodes.
>> topology.worker.childopts is what you set in your topology conf if you want
>> to add something more to the command line.
>>
>>
>> - Bobby
>>
>>
>>
>> On Tuesday, July 25, 2017, 11:50:04 PM CDT, sam mohel <
>> sammoh...@gmail.com> wrote:
>>
>>
>> i'm using 0.10.2 version . i tried to write in the code
>> conf.put(Config.WORKER_ CHILDOPTS, "-Xmx4g");
>> conf.put(Config.SUPERVISOR_ CHILDOPTS, "-Xmx4g");
>>
>> but i didn't touch any affect . Did i write the right configurations ?
>> Does this value is the largest ?
>>
>>
>>
>

Reply via email to