Can I not use tuple timeout?

[이승진 <sw...@navercorp.com>]

Dear all,
 
AFAIK, spout 'assumes' processing a tuple is failed when it does not accept ack in timeout interval.
 
But I found that even if spout's fail method is called, that tuple is still running through topology i.e other bolts are still processing that tuple.
 
So actually failed tuple is not failed but just delayed.
 
I think I can configure timeout value bigger, but I want to know if there's a way to avoid using spout's timeout 
 
Sincerly
 

Re: Can I not use tuple timeout?

[ja...@yahoo.com.tw]

Hi,
You are correct. You can set time-out longer by setting config. However, if you don't want to use ack feature, you can set number of acker to 0. By this way, your topology is running on an unreliable way. In other words, all of your tuple will not be tracked.

Best regards,
James Fu


> 이승진 <sw...@navercorp.com> 於 2014/6/18 下午5:29 寫道：
> 
> Dear all,
> 
>  
> 
> AFAIK, spout 'assumes' processing a tuple is failed when it does not accept ack in timeout interval.
> 
>  
> 
> But I found that even if spout's fail method is called, that tuple is still running through topology i.e other bolts are still processing that tuple.
> 
>  
> 
> So actually failed tuple is not failed but just delayed.
> 
>  
> 
> I think I can configure timeout value bigger, but I want to know if there's a way to avoid using spout's timeout 
> 
>  
> 
> Sincerly
> 
>  
> 
>