storm-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Rudraneel chakraborty <rudraneel.chakrabo...@gmail.com>
Subject Re: Need Help regarding topology with numWorker>1
Date Sat, 13 Feb 2016 05:43:02 GMT
Thanks for the reply. So after some thinking , i figured if i shorten the
size of the worker incoming queue , i can create the scenario where using
more than one worker might result in better performance. Any thoughts on
how to do that?

The property topology, receiver.buffer.size should be the the key as
mentioned here
http://www.michael-noll.com/blog/2013/06/21/understanding-storm-internal-message-buffers/

But this jira issue says this property is no longer used
https://issues.apache.org/jira/plugins/servlet/mobile#issue/STORM-596
Any thoughts on how to change the incoming queue size of the workers?

On Thursday, 11 February 2016, Matthias J. Sax <mjsax@apache.org> wrote:

> I am not sure what you mean:
>
>   - number of worker slots per supervisor
> or
>   - topology parameter "number of workers"
>
> Can you clarify?
>
> -Matthias
>
> On 02/11/2016 05:14 AM, anshu shukla wrote:
> > Not  like that..  But i have used workers equal to number of cores. Each
> > vm with 8 corea.
> >
> > On 11 Feb 2016 9:07 am, "Rudraneel chakraborty"
> > <rudraneel.chakraborty@gmail.com <javascript:;>
> > <mailto:rudraneel.chakraborty@gmail.com <javascript:;>>> wrote:
> >
> >     more than one worker on same node ? Did u use custom schedule r?
> >     because by default, the workers would be spread throughout the
> cluster
> >
>
>

-- 
Rudraneel Chakraborty
Carleton University Real Time and Distributed Systems Reserach

Mime
View raw message