If anybody reading other than OP is also affected by this and can provide 
minimally a reproducing example or an affected timeframe on a given 
instance, this will be the minimum information needed to look into a 
potential issue. 

I'm continuing to monitor this thread, and I hope we can get this addressed 
as soon as possible, as soon as it's demonstrated/repro'd.

On Monday, February 23, 2015 at 6:46:49 PM UTC-5, Kaan Soral wrote:
>
>   rate: 500/s
>>
>>   bucket_size: 100
>>
>>   retry_parameters:
>>
>>     task_retry_limit: 6
>>
>>     min_backoff_seconds: 2
>>
>>     max_doublings: 3
>>
>>
> Although my queue configuration is broad enough to handle occasional 
> internal failures, I noticed and verified that the taskqueue leaves some 
> tasks unexecuted
> ( 1% to 10%, happens when you burst tasks / run a mapreduce job [custom] - 
> happens both with normal instances and basic_scaling/B4 instances )
>
> I first noticed the issue when some operations that should have done were 
> left undone
>
> Than I inspected the taskqueue execution with a custom routine that tracks 
> / counts ingoing and executing tasks, a routine that I perfected long ago, 
> and noticed the missing executions
>
> The issue isn't persistent, after a re-deployment and re-test, the same 
> routine managed to traverse all the entities as it's supposed to
>
> TL;DR - some taskqueue tasks silently fail to execute, this should never 
> happen, but it happens very frequently without any reason, causes damage 
> and confusion
>

-- 
You received this message because you are subscribed to the Google Groups 
"Google App Engine" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
To post to this group, send email to [email protected].
Visit this group at http://groups.google.com/group/google-appengine.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-appengine/b97a79e6-cb98-4b34-b9c6-59b76efea41c%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to