Assuming each failure in the code is accompanied by collector.reportError(ex) (aka BasicBolt) then you would see an exception in nimbus. If there are many other errors, then it may not be the exception you are looking for.
To get more fidelity you would need to send all errors to ELK stack (that's what we do) and filter by id. Itai ________________________________ From: Simon Cooper <[email protected]> Sent: Monday, October 13, 2014 2:58 PM To: [email protected] Subject: Finding out why a tuple failed Is there any possible way, either through logging or programmatically, to find out why a tuple failed? If it timed out, which bolts it was waiting for acks from in the tuple tree, and if it was explicitly failed, which bolt failed it? I'm having a hell of a time trying to debug a complex topology that is not acking any of its tuples back at the spout :( Thanks, SimonC
