Hi,
I am modelling the performance of storm topologies. To model complete latency I need to account for the latency from the final "sink" component in the topology to the Acker (where the clock is stopped on the CL measurement). I have a way to track tuple routing within a topology, however tuples sent to system component are not covered by this. I was wondering is someone could explain how the acker is connected to the topology components (I am having trouble identifying where in the code base this takes place) and what type of grouping they use? Is there any intelligence to this routing, i.e. will an executor always ack to an Acker on the same WP and if not then at least a WP on the same Host, or is it more like a shuffle? Any help with the above would be appreciated. I really want to avoid re-implementing the Acker bolt myself. Cheers, Thomas Cooper PhD Student Newcastle University, School of Computer Science W: http://www.tomcooper.org.uk | Twitter: @tomncooper<https://twitter.com/tomncooper>
