Hi, I am not sure, but I doubt that BaseBasicBolt does ack automatically. Process-Latency should be lower, if a tuple is acked before execute finishes. So if you ack within execute, this should be normal.
For complete latency at spout you are right. If it should 0, it raises the question if you enable fault-tolerance (ie, assign message IDs at the spout?). Latency can only be measure if ID are assigned and proper anchoring in done in bolts. See here for more details: https://storm.apache.org/documentation/Guaranteeing-message-processing.html -Matthias On 07/27/2015 09:55 PM, Kashyap Mhaisekar wrote: > Hi, > My topology is based on BaseBasicBolt and hence the ack method should > done after the execute method. But I see that the Process Latency is > much lower than Execute Latency should it not be the other way round? > Any reasons why this happens? > > Also, my topology shows the "complete latency" in Spout as 0. Should > this not indicate the overall time taken for a message to get completely > acked? meaning the message getting totally processed? > > Thanks > Kashyap >
signature.asc
Description: OpenPGP digital signature
