[GitHub] bornej commented on issue #2692: Making emit, ack, and fail thread safe

[GitBox <gi...@apache.org>]

bornej commented on issue #2692: Making emit, ack, and fail thread safe
URL: https://github.com/apache/incubator-heron/pull/2692#issuecomment-390241133
 
 
   Hi, 
   while investigating the possibility of using multi-threaded bolt/spouts, I stumbled upon this PR.
   I don't know if this is the appropriate place to ask but I'm stuck with some questions...
   
   From what I understand, in each Heron instance there is only one slave thread doing bolt/spout computation (and a gateway thread used for communications with the stream manager). But after reading this discussion I'm a bit confused
   
   @jerrypeng 
   > We have some use cases in which users will want to emit and ack or fail in different threads.
   
   @srkukarni 
   > Users can(and do) have concurrent threads today. 
   > ... imagine this situation
   > 1. User Bolt has two 'worker' threads that actually do some work and use some kind of queue to put 
   > their acks/fails in the main process thread.
    
   Is it currently possible for a user to create a multi-threaded Bolt/spout? (Without altering HeronInstance implementation-> FixedThreadPool size) 
   If so, could someone help me figure out how to achieve that?
   
   I'm very new to Heron so I hope you will forgive me if my question seems stupid.
   
   I understand that Heron philosophy is to use "single"-threaded Instances (bolt/spouts) and why this design choice was made but I'm wondering if some computation tasks could benefit from multi-threading...
   
   Thanks for your help and your work.
   Best Regards.
   Jonathan.
   

----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
users@infra.apache.org


With regards,
Apache Git Services