Keep in mind you'll need to synchronize the OutputCollector when your NIO response workers handle the returned requests as OutputCollector is not thread safe.
Michael Rose (@Xorlev <https://twitter.com/xorlev>) Senior Platform Engineer, FullContact <http://www.fullcontact.com/> [email protected] On Mon, Dec 15, 2014 at 9:20 AM, Itai Frenkel <[email protected]> wrote: > > Hi, > > > Any non-blocking bolt does not push back on the previous bolt if it is > out of resources. So you should consider using max-spout-pending for spout > level throttling. > > > Regards, > > Itai > ------------------------------ > *From:* Idan Fridman <[email protected]> > *Sent:* Monday, December 15, 2014 10:19 AM > *To:* [email protected] > *Subject:* Using AsyncHttpReuqest inside a Bolt > > Hi All, > My bolt need to dispatch async request to remote service. > > I am using AsyncHttpReuest library( > https://github.com/AsyncHttpClient/async-http-client) which based on NIO > channels to get the response asynchronously while not allocating Thread for > each request. > > I was wondering if any side-effects could cause this implementation > within Storm Bolt ? > > thank you. >
