Are you settting numWorkers in you topology config like here
https://github.com/apache/storm/blob/master/examples/storm-starter/src/jvm/storm/starter/WordCountTopology.java#L92
On Thu, Feb 26, 2015, at 12:40 PM, Srividhya Shanmugam wrote:
> Thanks for the reply Harsha. We have distributed supervisor nodes (2)
> and a nimbus node. The storm.yaml file has topology.workers property
> commented out. When
a topology gets submitted that has one spout and a bolt with
parallelism hint of 10 for each, before 0.9.3 upgrade storm distributes
this work across multiple worker process. The supervisor slots
configured in the three nodes has a value 6701, 6702, 6703.
>
> When such topology is submitted in storm now(after the upgrade), it’s
> just one worker process that gets created with 21 executor threads.
> Shouldn’t storm distribute
the work?
>
> *From:* Harsha [mailto:storm@harsha.io]
>
> *Sent:* Thursday, February 26, 2015 3:33 PM *To:*
> user@storm.apache.org *Subject:* Re: Why is the toplogy.workers is
> hardcoded to 1
>
> Srividhya,
> Storm topologies requires at least one worker to be available to run.
> Hence the config will set as 1 for the topology.workers as default
> value. Can you explain in more detail what you are trying to achieve.
> Thanks,
> Harsha
>
>
> On Thu, Feb 26, 2015, at 12:12 PM, Srividhya Shanmugam wrote:
>> I have commented this property in the storm.yaml. But still it always
>> defaults to 1 after we upgraded storm to 0.9.3. Any idea why its
>> hardcoded?
>>
>> This email and any files transmitted with it are confidential,
>> proprietary and intended solely for the individual or entity to whom
>> they are addressed. If you have received this email in error please
>> delete it immediately.
>
>
> This email and any files transmitted with it are confidential,
> proprietary and intended solely for the individual or entity to whom
> they are addressed. If you have received this email in error please
> delete it immediately.
|