storm-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Kyle Nusbaum <>
Subject Re: Assignment of threads to tcp ports
Date Thu, 01 Sep 2016 16:52:44 GMT
Yep! That's correct. 

If you implemented your own scheduler, you could write one that gave more control of ports
to the cluster users, but it's not a simple task.
 -- Kyle 

    On Thursday, September 1, 2016 3:35 AM, Richards Peter <> wrote:

 Is it the pluggable scheduler that is being discussed here?

Richards Peter.

On Wed, Aug 31, 2016 at 11:44 PM, Kyle Nusbaum <> wrote:

There's no API to do that currently. It's entirely up to the scheduler and will likely stay
that way. I think creating an API to control this sort of thing is a direction we don't want
to go in with Storm. -- Kyle 

    On Wednesday, August 31, 2016 8:10 AM, Walid Aljoby <> wrote:

 Hi Anshu,
Yeah, correct. (6700-6703). 
Thanks and Best Walid

      From: anshu shukla <>
 To:; Walid Aljoby <> 
 Sent: Wednesday, August 31, 2016 9:00 PM
 Subject: Re: Assignment of threads to tcp ports
By tcp port you mean Supervisor port .
On Wed, Aug 31, 2016 at 6:24 PM, Walid Aljoby <> wrote:

Hi everyone,
Is it easier to specify in which tcp port the tasks (threads) will be assigned?Any API can
help to do that?
Thank You--Regards

Thanks & Regards,
Anshu Shukla



View raw message