we plan to contribute our UserDefinedScheduler to community this or next month. https://issues.apache.org/jira/browse/STORM-2033 the UserDefinedScheduler support specifying nodes and ports for topology and its components.
2016-09-02 0:52 GMT+08:00 Kyle Nusbaum <[email protected]>: > 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 < > [email protected]> wrote: > > > Is it the pluggable scheduler that is being discussed here? > http://storm.apache.org/releases/1.0.1/Storm-Scheduler.html > > Richards Peter. > > On Wed, Aug 31, 2016 at 11:44 PM, Kyle Nusbaum <[email protected]> > 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 < > [email protected]> wrote: > > > Hi Anshu, > > Yeah, correct. (6700-6703). > > - > Thanks and Best > Walid > > > ------------------------------ > *From:* anshu shukla <[email protected]> > *To:* [email protected]; Walid Aljoby <[email protected]> > *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 <[email protected]> > 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 > > > > > > > >
