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

Reply via email to