[google-appengine] Re: Request was aborted after waiting too long to attempt to service your request

['Harmit Rishi (Cloud Platform Support)' via Google App Engine]

Hello, 

Thank you for using Google Groups!

Just going off the amount of information provided on your posting, I 
believe the following documentation here 
 
regarding *Google App Engine request timer *would be of some use to you. 
Additionally, this type of issue is usually encountered when there is a 
sudden high spike in incoming requests that exceed the services capacity. 
However, App start-up time taking longer than the response time may cause 
this as well. You may feel free to verify if the documentation shared above 
is able to provide you the necessary information to remedy this issue.

I hope this helps!

-- 
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 google-appengine+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-appengine/eee4a721-083f-4369-b2ae-f0849062fa1e%40googlegroups.com.

[google-appengine] Re: "Request was aborted after waiting too long to attempt to service your request." sprees

[Jason Collins]

More min_idle_instances (at an increased cost of course) will help service 
bursts and avoid these pending queue timeouts.


On Monday, 2 November 2015 18:05:30 UTC-8, Kaan Soral wrote:
>
> Yes, AppEngine can't handle bursts well, so the solution is to slow things 
> down
>
> Actually, there are speed limits on a lot of things that are usually not 
> advertised well, if you are getting these kind of errors, try to slow 
> things down and see how it goes
>
> Slowing things down is also pretty challenging, much harder than building 
> stuff that will scale
>
> On Monday, November 2, 2015 at 6:48:57 PM UTC+3, Alexandra wrote:
>>
>> Hi,
>>
>> Did you find the reason of these errors?
>>
>> I also see a lot of them. The time which is elapsed is about 10 min, so 
>> it seems that there are tasks that are stuck for some reason in the task 
>> queue.
>>
>> Any insights on that?
>>
>> Thanks
>> Alexandra
>>
>> On Saturday, April 11, 2015 at 8:02:34 PM UTC+3, Kaan Soral wrote:
>>>
>>> "Request was aborted after waiting too long to attempt to service your 
>>> request."
>>>
>>> I've been seeing these messages a lot lately, momentarily many requests 
>>> log these errors, it floods the error logs
>>>
>>> Anyone else?
>>>
>>

-- 
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 google-appengine+unsubscr...@googlegroups.com.
To post to this group, send email to google-appengine@googlegroups.com.
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/7b7bca79-e617-4660-bae3-dc0970c6c9e1%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[google-appengine] Re: "Request was aborted after waiting too long to attempt to service your request." sprees

[Nick (Cloud Platform Support)]

@Kaan Soral

I think the issue cannot be adequately narrowed-down from the information 
provided, and with only the commonality of seeing the "Request was aborted 
after waiting too long to attempt to service your request." error, it's 
impossible to determine that the same issue is being reported by Alexandra 
- that's the reason why a proper issue report 
 is needed (see in 
that link a template).

There doesn't seem to be a basis for inferring the general statement that 
"AppEngine can't handle bursts well". This is especially so when the 
justification for the statement refers to a very specific use-case related 
to errors seen in a task queue with specific scaling settings. These 
scaling settings might be at the heart of the original issue reported at 
the top of the thread. Having a minimum and maximum of 1 idle instance 
doesn't exactly lend itself to managing every possible burst. 

Depending on the request pattern and start-up time, you could see strange 
scenarios where requests are building up in pending queues, instances are 
firing up and then shutting down after becoming idle, with the pending 
queues migrating and merging among these rapidly spawning and de-spawning 
instances. Requests in a rather short pending queue dealing with this 
potentially-volatile setup would not be seen to scale well, and many could 
in fact reach a timeout without getting to an instance. Again, this is a 
plausible explanation, but not confirmed by any real data. You can read in 
the docs some advice on how the scaling settings work 
, and how to best design 
for scaling events 
. Of course, as 
usual, if you have a specific issue, feel free to provide a report in the 
issue tracker .

On Monday, November 2, 2015 at 9:05:30 PM UTC-5, Kaan Soral wrote:
>
> Yes, AppEngine can't handle bursts well, so the solution is to slow things 
> down
>
> Actually, there are speed limits on a lot of things that are usually not 
> advertised well, if you are getting these kind of errors, try to slow 
> things down and see how it goes
>
> Slowing things down is also pretty challenging, much harder than building 
> stuff that will scale
>
> On Monday, November 2, 2015 at 6:48:57 PM UTC+3, Alexandra wrote:
>>
>> Hi,
>>
>> Did you find the reason of these errors?
>>
>> I also see a lot of them. The time which is elapsed is about 10 min, so 
>> it seems that there are tasks that are stuck for some reason in the task 
>> queue.
>>
>> Any insights on that?
>>
>> Thanks
>> Alexandra
>>
>> On Saturday, April 11, 2015 at 8:02:34 PM UTC+3, Kaan Soral wrote:
>>>
>>> "Request was aborted after waiting too long to attempt to service your 
>>> request."
>>>
>>> I've been seeing these messages a lot lately, momentarily many requests 
>>> log these errors, it floods the error logs
>>>
>>> Anyone else?
>>>
>>

-- 
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 google-appengine+unsubscr...@googlegroups.com.
To post to this group, send email to google-appengine@googlegroups.com.
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/a3d5858f-6d8b-4656-953a-2df06119c94c%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[google-appengine] Re: "Request was aborted after waiting too long to attempt to service your request." sprees

[Alexandra]

Hi,

Did you find the reason of these errors?

I also see a lot of them. The time which is elapsed is about 10 min, so it 
seems that there are tasks that are stuck for some reason in the task queue.

Any insights on that?

Thanks
Alexandra

On Saturday, April 11, 2015 at 8:02:34 PM UTC+3, Kaan Soral wrote:
>
> "Request was aborted after waiting too long to attempt to service your 
> request."
>
> I've been seeing these messages a lot lately, momentarily many requests 
> log these errors, it floods the error logs
>
> Anyone else?
>

-- 
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 google-appengine+unsubscr...@googlegroups.com.
To post to this group, send email to google-appengine@googlegroups.com.
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/aece30e7-9ee5-4f5b-95e2-775e91430eb1%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[google-appengine] Re: "Request was aborted after waiting too long to attempt to service your request." sprees

[Nick (Cloud Platform Support)]

Hey Alexandra,

If you're experiencing an issue on the platform, the best way to report 
that issue and get help with it would either be to post on a Stack Exchange 
site (Stack Overflow  for example), in the case 
that you think the issue is related to your own code, or on the public 
issue tracker for App Engine 
, if, having 
followed all documentation and fully understanding the issue could not be 
in your code, you suspect that the issue might be on our side, which we can 
fix. 

Unfortunately, this thread contains next-to-zero useful debugging 
information other than some instance stats (F2 instance) and a vague 
indication that the error coincides with bursts of activity, so this thread 
can't really function as an issue report which is actionable.

So, I wish you or anybody else experiencing issues who reads this thread 
the best of luck in reporting your issue through one of the forms above, 
and hopefully with providing enough information, you can have someone help 
you out with a solution for your code or a tracking number for a solution 
to be patched, depending on the situation.

On Monday, November 2, 2015 at 10:48:57 AM UTC-5, Alexandra wrote:
>
> Hi,
>
> Did you find the reason of these errors?
>
> I also see a lot of them. The time which is elapsed is about 10 min, so it 
> seems that there are tasks that are stuck for some reason in the task queue.
>
> Any insights on that?
>
> Thanks
> Alexandra
>
> On Saturday, April 11, 2015 at 8:02:34 PM UTC+3, Kaan Soral wrote:
>>
>> "Request was aborted after waiting too long to attempt to service your 
>> request."
>>
>> I've been seeing these messages a lot lately, momentarily many requests 
>> log these errors, it floods the error logs
>>
>> Anyone else?
>>
>

-- 
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 google-appengine+unsubscr...@googlegroups.com.
To post to this group, send email to google-appengine@googlegroups.com.
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/d54b3bd0-396b-48dc-a0f8-32b7168feca3%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[google-appengine] Re: "Request was aborted after waiting too long to attempt to service your request." sprees

[Kaan Soral]

Yes, AppEngine can't handle bursts well, so the solution is to slow things 
down

Actually, there are speed limits on a lot of things that are usually not 
advertised well, if you are getting these kind of errors, try to slow 
things down and see how it goes

Slowing things down is also pretty challenging, much harder than building 
stuff that will scale

On Monday, November 2, 2015 at 6:48:57 PM UTC+3, Alexandra wrote:
>
> Hi,
>
> Did you find the reason of these errors?
>
> I also see a lot of them. The time which is elapsed is about 10 min, so it 
> seems that there are tasks that are stuck for some reason in the task queue.
>
> Any insights on that?
>
> Thanks
> Alexandra
>
> On Saturday, April 11, 2015 at 8:02:34 PM UTC+3, Kaan Soral wrote:
>>
>> "Request was aborted after waiting too long to attempt to service your 
>> request."
>>
>> I've been seeing these messages a lot lately, momentarily many requests 
>> log these errors, it floods the error logs
>>
>> Anyone else?
>>
>

-- 
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 google-appengine+unsubscr...@googlegroups.com.
To post to this group, send email to google-appengine@googlegroups.com.
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/e5949fb2-50fd-41d2-b0f7-7ba5bd441b58%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[google-appengine] Re: Request was aborted after waiting too long to attempt to service your request

[Michael (Cloud Platform Support)]

Hey everyone,

There are a few possible causes for this error message. Could you please 
private message me the app-ids for the projects currently experiencing this 
issue so I can investigate further?

Cheers!

On Tuesday, June 23, 2015 at 5:01:42 AM UTC-4, PK wrote:

 For the past few days I see a lot of aborted calls with the message

 Request was aborted after waiting too long to attempt to service your 
 request”

 It comes from deferred and other queued requests, I have not seen any 
 change with interactive calls. Has anybody else noticed similar behavior? I 
 use the scheduler with the default settings. Has anything changed?

 Thanks,
 PK
 p...@gae123.com



  


-- 
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 google-appengine+unsubscr...@googlegroups.com.
To post to this group, send email to google-appengine@googlegroups.com.
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/1b94b3a2-93e8-4f6d-8a85-4e3ea6e2c6a8%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[google-appengine] Re: Request was aborted after waiting too long to attempt to service your request

[Kaan Soral]

I also experienced these again recently, they are part of the rare 
appengine issue bursts, rarely things go wrong and deadline exceptions, 
transient errors and these errors arise, it's expected (at least I come to 
expect them)

I used to experience these every day, but throttling my routines prevented 
them

The sad truth is, appengine can't handle too much acceleration, bursting of 
tasks etc. - so throttling the routine that caused these errors will fix 
the issue - it's what I did, after reducing my taskqueue rates and buckets, 
the issue was gone

-- 
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 google-appengine+unsubscr...@googlegroups.com.
To post to this group, send email to google-appengine@googlegroups.com.
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/12fb4c3f-1945-4644-9925-0cf312927b63%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[google-appengine] Re: Request was aborted after waiting too long to attempt to service your request

[Eric Froemling]

I started seeing this too a day or so ago too (somewhere around 9-10PM EST 
monday night). For me it's not limited to deferred requests; I'm seeing 
large numbers of these failures across all my requests.  I've found I can 
keep things under control by cranking max_idle_instances way up (I usually 
leave it at zero), but I really hope this gets resolved soon.  I also 
noticed this exact same thing happening several weeks back; in that case it 
lasted started on a saturday and seemed to get resolved the following 
monday.

Anyone else seeing this or know what could be happening here?
Thanks,
-Eric

On Tuesday, June 23, 2015 at 2:01:42 AM UTC-7, PK wrote:

 For the past few days I see a lot of aborted calls with the message

 Request was aborted after waiting too long to attempt to service your 
 request”

 It comes from deferred and other queued requests, I have not seen any 
 change with interactive calls. Has anybody else noticed similar behavior? I 
 use the scheduler with the default settings. Has anything changed?

 Thanks,
 PK
 p...@gae123.com javascript:



  


-- 
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 google-appengine+unsubscr...@googlegroups.com.
To post to this group, send email to google-appengine@googlegroups.com.
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/b18882aa-d5e4-4d01-8297-7479f6b2ca51%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[google-appengine] Re: Request was aborted after waiting too long to attempt to service your request. sprees

[Kaan Soral]

They are all *taskqueue* tasks on a *module* with *F2*'s

I think out of the 3, the module aspect might be the cause, as I don't 
experience the issue on other systems

On Wednesday, April 22, 2015 at 11:42:31 AM UTC+3, Mario wrote:

 Hi,

 What are those requests that result in errors?

 On Sunday, April 19, 2015 at 8:53:24 PM UTC+2, Kaan Soral wrote:

 I started regularly getting 200-1000 of these in batches

 Not sure what to do about them

 My other app that handles more requests never has them, I'm guessing they 
 are related to instance bursts, the app that experiences the issue probably 
 bursts instances too much

 I don't think the issue is memory related, as in that case, the instances 
 usually die with the critical memory error

 On Tuesday, April 14, 2015 at 10:58:20 AM UTC+3, Mario wrote:

 Hi Kaan,

 This error is sometimes created by your requests going over the memory 
 limit of your instance. You could try to update the instance to F4 or to 
 make your requests to process data in smaller chunks. 

 Mario

 On Monday, April 13, 2015 at 11:52:19 PM UTC+2, Kaan Soral wrote:

 Hi Cody

 That makes an extreme amount of sense, it would also explain a lot of 
 the inconsistent behaviours of appengine, especially invisibly exhausted 
 taskqueue retries

 I checked the logs, however, although my log storage is more than 
 enough, for some reason the phrase aborted/.*aborted.* didn't produce 
 any results, didn't pursue the issue further, the log routines are 
 annoying 
 at best

 Mario, the instances are:
 instance_class: F2
 automatic_scaling:
   min_idle_instances: 1
   max_idle_instances: 1
   max_pending_latency: 900ms

 The issue has been happening in bursts lately

 On Monday, April 13, 2015 at 10:28:00 PM UTC+3, Cody Landgrebe wrote:

 Kaan,

 Looking at the SDK release notes and current version of GAE console 
 app engine release 1.9.19 notes have not been published yet; but from 
 research my assumption is that the logging level was changed from info to 
 error in the latest version. If you look through your logs prior to the 
 move to .19 I assume that you will have the same messages but logged as 
 info.

 On Saturday, April 11, 2015 at 12:02:34 PM UTC-5, Kaan Soral wrote:

 Request was aborted after waiting too long to attempt to service 
 your request.

 I've been seeing these messages a lot lately, momentarily many 
 requests log these errors, it floods the error logs

 Anyone else?



-- 
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 google-appengine+unsubscr...@googlegroups.com.
To post to this group, send email to google-appengine@googlegroups.com.
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/3eec7dc1-b5f9-4aa2-a4d6-669a25913ff3%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[google-appengine] Re: Request was aborted after waiting too long to attempt to service your request. sprees

[Mario]

Hi,

What are those requests that result in errors?

On Sunday, April 19, 2015 at 8:53:24 PM UTC+2, Kaan Soral wrote:

 I started regularly getting 200-1000 of these in batches

 Not sure what to do about them

 My other app that handles more requests never has them, I'm guessing they 
 are related to instance bursts, the app that experiences the issue probably 
 bursts instances too much

 I don't think the issue is memory related, as in that case, the instances 
 usually die with the critical memory error

 On Tuesday, April 14, 2015 at 10:58:20 AM UTC+3, Mario wrote:

 Hi Kaan,

 This error is sometimes created by your requests going over the memory 
 limit of your instance. You could try to update the instance to F4 or to 
 make your requests to process data in smaller chunks. 

 Mario

 On Monday, April 13, 2015 at 11:52:19 PM UTC+2, Kaan Soral wrote:

 Hi Cody

 That makes an extreme amount of sense, it would also explain a lot of 
 the inconsistent behaviours of appengine, especially invisibly exhausted 
 taskqueue retries

 I checked the logs, however, although my log storage is more than 
 enough, for some reason the phrase aborted/.*aborted.* didn't produce 
 any results, didn't pursue the issue further, the log routines are annoying 
 at best

 Mario, the instances are:
 instance_class: F2
 automatic_scaling:
   min_idle_instances: 1
   max_idle_instances: 1
   max_pending_latency: 900ms

 The issue has been happening in bursts lately

 On Monday, April 13, 2015 at 10:28:00 PM UTC+3, Cody Landgrebe wrote:

 Kaan,

 Looking at the SDK release notes and current version of GAE console app 
 engine release 1.9.19 notes have not been published yet; but from 
 research my assumption is that the logging level was changed from info to 
 error in the latest version. If you look through your logs prior to the 
 move to .19 I assume that you will have the same messages but logged as 
 info.

 On Saturday, April 11, 2015 at 12:02:34 PM UTC-5, Kaan Soral wrote:

 Request was aborted after waiting too long to attempt to service 
 your request.

 I've been seeing these messages a lot lately, momentarily many 
 requests log these errors, it floods the error logs

 Anyone else?



-- 
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 google-appengine+unsubscr...@googlegroups.com.
To post to this group, send email to google-appengine@googlegroups.com.
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/570dfd18-afe0-4165-8bd6-e8f1f2a86da6%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[google-appengine] Re: Request was aborted after waiting too long to attempt to service your request. sprees

[Kaan Soral]

I started regularly getting 200-1000 of these in batches

Not sure what to do about them

My other app that handles more requests never has them, I'm guessing they 
are related to instance bursts, the app that experiences the issue probably 
bursts instances too much

I don't think the issue is memory related, as in that case, the instances 
usually die with the critical memory error

On Tuesday, April 14, 2015 at 10:58:20 AM UTC+3, Mario wrote:

 Hi Kaan,

 This error is sometimes created by your requests going over the memory 
 limit of your instance. You could try to update the instance to F4 or to 
 make your requests to process data in smaller chunks. 

 Mario

 On Monday, April 13, 2015 at 11:52:19 PM UTC+2, Kaan Soral wrote:

 Hi Cody

 That makes an extreme amount of sense, it would also explain a lot of the 
 inconsistent behaviours of appengine, especially invisibly exhausted 
 taskqueue retries

 I checked the logs, however, although my log storage is more than enough, 
 for some reason the phrase aborted/.*aborted.* didn't produce any 
 results, didn't pursue the issue further, the log routines are annoying at 
 best

 Mario, the instances are:
 instance_class: F2
 automatic_scaling:
   min_idle_instances: 1
   max_idle_instances: 1
   max_pending_latency: 900ms

 The issue has been happening in bursts lately

 On Monday, April 13, 2015 at 10:28:00 PM UTC+3, Cody Landgrebe wrote:

 Kaan,

 Looking at the SDK release notes and current version of GAE console app 
 engine release 1.9.19 notes have not been published yet; but from 
 research my assumption is that the logging level was changed from info to 
 error in the latest version. If you look through your logs prior to the 
 move to .19 I assume that you will have the same messages but logged as 
 info.

 On Saturday, April 11, 2015 at 12:02:34 PM UTC-5, Kaan Soral wrote:

 Request was aborted after waiting too long to attempt to service your 
 request.

 I've been seeing these messages a lot lately, momentarily many requests 
 log these errors, it floods the error logs

 Anyone else?



-- 
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 google-appengine+unsubscr...@googlegroups.com.
To post to this group, send email to google-appengine@googlegroups.com.
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/dd95effc-f4a9-46c5-8e06-630b8072093e%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[google-appengine] Re: Request was aborted after waiting too long to attempt to service your request. sprees

[Mario]

Hi Kaan,

This error is sometimes created by your requests going over the memory 
limit of your instance. You could try to update the instance to F4 or to 
make your requests to process data in smaller chunks. 

Mario

On Monday, April 13, 2015 at 11:52:19 PM UTC+2, Kaan Soral wrote:

 Hi Cody

 That makes an extreme amount of sense, it would also explain a lot of the 
 inconsistent behaviours of appengine, especially invisibly exhausted 
 taskqueue retries

 I checked the logs, however, although my log storage is more than enough, 
 for some reason the phrase aborted/.*aborted.* didn't produce any 
 results, didn't pursue the issue further, the log routines are annoying at 
 best

 Mario, the instances are:
 instance_class: F2
 automatic_scaling:
   min_idle_instances: 1
   max_idle_instances: 1
   max_pending_latency: 900ms

 The issue has been happening in bursts lately

 On Monday, April 13, 2015 at 10:28:00 PM UTC+3, Cody Landgrebe wrote:

 Kaan,

 Looking at the SDK release notes and current version of GAE console app 
 engine release 1.9.19 notes have not been published yet; but from 
 research my assumption is that the logging level was changed from info to 
 error in the latest version. If you look through your logs prior to the 
 move to .19 I assume that you will have the same messages but logged as 
 info.

 On Saturday, April 11, 2015 at 12:02:34 PM UTC-5, Kaan Soral wrote:

 Request was aborted after waiting too long to attempt to service your 
 request.

 I've been seeing these messages a lot lately, momentarily many requests 
 log these errors, it floods the error logs

 Anyone else?



-- 
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 google-appengine+unsubscr...@googlegroups.com.
To post to this group, send email to google-appengine@googlegroups.com.
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/f3b499bc-a35f-4f01-9e34-8c9589b4958c%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[google-appengine] Re: Request was aborted after waiting too long to attempt to service your request. sprees

[Cody Landgrebe]

Kaan,

Looking at the SDK release notes and current version of GAE console app 
engine release 1.9.19 notes have not been published yet; but from research 
my assumption is that the logging level was changed from info to error in 
the latest version. If you look through your logs prior to the move to .19 
I assume that you will have the same messages but logged as info.

On Saturday, April 11, 2015 at 12:02:34 PM UTC-5, Kaan Soral wrote:

 Request was aborted after waiting too long to attempt to service your 
 request.

 I've been seeing these messages a lot lately, momentarily many requests 
 log these errors, it floods the error logs

 Anyone else?


-- 
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 google-appengine+unsubscr...@googlegroups.com.
To post to this group, send email to google-appengine@googlegroups.com.
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/c45d987d-83d3-4714-bde9-20f88ea089d2%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[google-appengine] Re: Request was aborted after waiting too long to attempt to service your request. sprees

[Kaan Soral]

Hi Cody

That makes an extreme amount of sense, it would also explain a lot of the 
inconsistent behaviours of appengine, especially invisibly exhausted 
taskqueue retries

I checked the logs, however, although my log storage is more than enough, 
for some reason the phrase aborted/.*aborted.* didn't produce any 
results, didn't pursue the issue further, the log routines are annoying at 
best

Mario, the instances are:
instance_class: F2
automatic_scaling:
  min_idle_instances: 1
  max_idle_instances: 1
  max_pending_latency: 900ms

The issue has been happening in bursts lately

On Monday, April 13, 2015 at 10:28:00 PM UTC+3, Cody Landgrebe wrote:

 Kaan,

 Looking at the SDK release notes and current version of GAE console app 
 engine release 1.9.19 notes have not been published yet; but from 
 research my assumption is that the logging level was changed from info to 
 error in the latest version. If you look through your logs prior to the 
 move to .19 I assume that you will have the same messages but logged as 
 info.

 On Saturday, April 11, 2015 at 12:02:34 PM UTC-5, Kaan Soral wrote:

 Request was aborted after waiting too long to attempt to service your 
 request.

 I've been seeing these messages a lot lately, momentarily many requests 
 log these errors, it floods the error logs

 Anyone else?



-- 
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 google-appengine+unsubscr...@googlegroups.com.
To post to this group, send email to google-appengine@googlegroups.com.
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/53ecd87f-f901-4a33-bcd9-b45513020dc6%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[google-appengine] Re: Request was aborted after waiting too long to attempt to service your request. sprees

[Mario]

In order to help you further, you'd need to provide more information about 
when you see those messages, kind of instances you're using, programming 
language, etc.

On Saturday, April 11, 2015 at 7:02:34 PM UTC+2, Kaan Soral wrote:

 Request was aborted after waiting too long to attempt to service your 
 request.

 I've been seeing these messages a lot lately, momentarily many requests 
 log these errors, it floods the error logs

 Anyone else?


-- 
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 google-appengine+unsubscr...@googlegroups.com.
To post to this group, send email to google-appengine@googlegroups.com.
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/35203f66-4a18-4458-9b53-63c9d86c9ee6%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[google-appengine] Re: Request was aborted after waiting too long to attempt to service your request

[Jason Collins]

Requests that hit your application are put into a queue waiting for an 
instance to become available. If those requests become 10-seconds old, they 
are cancelled (error to client).

The App Engine Scheduler may or may not attempt to spin up a new instance 
under this pressure (rules are black box and change from time to time). If 
it is able to spin up an instance, it will send the request to the cold 
(no warm up request) instance, though there is much debate (e.g., 
https://code.google.com/p/googleappengine/issues/detail?id=7865) about 
whether or not this should occur, especially for Java apps.

The only way to avoid these errors are to allocate Min Idle Instances, 
which keeps resident instances around to help in this specific case. These 
resident instances themselves can be somewhat confusing because they are 
really only used to serve when a dynamic instance cannot be found - i.e., 
basically under this pressure situation you've outlined. You'll find, in a 
more smoothly loaded case, that the resident instances can be very 
under-utilized as they are basically idle waiting for spikes. This too is 
the subject of much debate.

j

On Saturday, 25 January 2014 15:42:07 UTC-6, o...@haitov.com wrote:

 Hi,
 I'm experiencing a very strange issue with my app, App engine suddenly 
 can't deal with incoming requests and shows this message in the logs 
 without any error code and at information level ! 
 Sometimes all the incoming requests during a few minutes can return this 
 message and then everything goes back to normal !
 This is really bad as it is a front end that serves a mobile app and that 
 means that during this time the app is fully non functional :-(((

 @Google 
 Why isn't this message at error or warning level ? 


 Attached is a screenshot of the log message





-- 
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 google-appengine+unsubscr...@googlegroups.com.
To post to this group, send email to google-appengine@googlegroups.com.
Visit this group at http://groups.google.com/group/google-appengine.
For more options, visit https://groups.google.com/groups/opt_out.

[google-appengine] Re: Request was aborted after waiting too long to attempt to service your request.

[Jamie H]

Ikai,

I understand your response to this post but I'd like to let you know
what I have seen.  I see this error occasionally when my site has no
load.  Ie: 0 instances.  For example, in the middle of the night when
no users are on the site my cron runs and I receive this error.  To
prevent this I have created warmup cron jobs 1 minute before all my
real cron jobs.  So far this has worked, but sometimes I do see my
warmup cron jobs error out with this error.  This leads me to
believe this error can happen on cold starts ?


On Oct 21, 2:20 pm, Ikai Lan (Google) ikai.l+gro...@google.com
wrote:
 Adam,

 The reason this is happening is because your requests take too long to
 execute. App Engine apps will autoscale if they are generally kept as low
 latency requests. The average latency of your requests is 1ms, so we
 will not add instances. You will need to reduce the latency of your user
 facing calls to under 1000ms (we recommend 800ms, and 400ms) for best
 performance.

 Strategies to do this:

 - denormalize your data model to emphasize reads
 - move long running jobs to task queues

 Your web/user facing requests must be as fast as possible.

 --
 Ikai Lan
 Developer Programs Engineer, Google App Engine
 Blogger:http://googleappengine.blogspot.com
 Reddit:http://www.reddit.com/r/appengine
 Twitter:http://twitter.com/app_engine

 On Wed, Oct 20, 2010 at 3:17 PM, Adam Johnson
 adam.johnson.s...@gmail.comwrote:

  Hi folks,

  I'm getting tons of this error on my app id 'ipadsocial' yesterday and 
  today. Could you take a look? Maybe you should increase some of the 
  internal quotas for my app. It is paid app.

  Thanks,
  Adam

  Request was aborted after waiting too long to attempt to service your 
  request. This may happen sporadically when the App Engine serving cluster 
  is under unexpectedly high or uneven load. If you see this message 
  frequently, please contact the App Engine team.

   --
  You received this message because you are subscribed to the Google Groups
  Google App Engine group.
  To post to this group, send email to google-appeng...@googlegroups.com.
  To unsubscribe from this group, send email to
  google-appengine+unsubscr...@googlegroups.comgoogle-appengine%2bunsubscr...@googlegroups.com
  .
  For more options, visit this group at
 http://groups.google.com/group/google-appengine?hl=en.



-- 
You received this message because you are subscribed to the Google Groups 
Google App Engine group.
To post to this group, send email to google-appeng...@googlegroups.com.
To unsubscribe from this group, send email to 
google-appengine+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/google-appengine?hl=en.

Re: [google-appengine] Re: Request was aborted after waiting too long to attempt to service your request.

[Adam Johnson]

lkai,

Thanks for your response. That may explain for some other apps. In our case,
the app 'ipadsocial' is pretty much a pure backend app. Most of the load is
through cron and deferred jobs. Number of web front requests is close to
zero. If you try to visit http://ipadsocial.appspot.com, you will see. We
have almost no UI.

Adam

On Thu, Oct 21, 2010 at 2:36 PM, Jamie H ja...@mhztech.com wrote:

 Ikai,

 I understand your response to this post but I'd like to let you know
 what I have seen.  I see this error occasionally when my site has no
 load.  Ie: 0 instances.  For example, in the middle of the night when
 no users are on the site my cron runs and I receive this error.  To
 prevent this I have created warmup cron jobs 1 minute before all my
 real cron jobs.  So far this has worked, but sometimes I do see my
 warmup cron jobs error out with this error.  This leads me to
 believe this error can happen on cold starts ?


 On Oct 21, 2:20 pm, Ikai Lan (Google) 
 ikai.l+gro...@google.comikai.l%2bgro...@google.com
 
 wrote:
  Adam,
 
  The reason this is happening is because your requests take too long to
  execute. App Engine apps will autoscale if they are generally kept as low
  latency requests. The average latency of your requests is 1ms, so we
  will not add instances. You will need to reduce the latency of your user
  facing calls to under 1000ms (we recommend 800ms, and 400ms) for best
  performance.
 
  Strategies to do this:
 
  - denormalize your data model to emphasize reads
  - move long running jobs to task queues
 
  Your web/user facing requests must be as fast as possible.
 
  --
  Ikai Lan
  Developer Programs Engineer, Google App Engine
  Blogger:http://googleappengine.blogspot.com
  Reddit:http://www.reddit.com/r/appengine
  Twitter:http://twitter.com/app_engine
 
  On Wed, Oct 20, 2010 at 3:17 PM, Adam Johnson
  adam.johnson.s...@gmail.comwrote:
 
   Hi folks,
 
   I'm getting tons of this error on my app id 'ipadsocial' yesterday and
 today. Could you take a look? Maybe you should increase some of the internal
 quotas for my app. It is paid app.
 
   Thanks,
   Adam
 
   Request was aborted after waiting too long to attempt to service your
 request. This may happen sporadically when the App Engine serving cluster is
 under unexpectedly high or uneven load. If you see this message frequently,
 please contact the App Engine team.
 
--
   You received this message because you are subscribed to the Google
 Groups
   Google App Engine group.
   To post to this group, send email to google-appengine@googlegroups.com
 .
   To unsubscribe from this group, send email to
   google-appengine+unsubscr...@googlegroups.comgoogle-appengine%2bunsubscr...@googlegroups.com
 google-appengine%2bunsubscr...@googlegroups.comgoogle-appengine%252bunsubscr...@googlegroups.com
 
   .
   For more options, visit this group at
  http://groups.google.com/group/google-appengine?hl=en.
 
 

 --
 You received this message because you are subscribed to the Google Groups
 Google App Engine group.
 To post to this group, send email to google-appeng...@googlegroups.com.
 To unsubscribe from this group, send email to
 google-appengine+unsubscr...@googlegroups.comgoogle-appengine%2bunsubscr...@googlegroups.com
 .
 For more options, visit this group at
 http://groups.google.com/group/google-appengine?hl=en.



-- 
You received this message because you are subscribed to the Google Groups 
Google App Engine group.
To post to this group, send email to google-appeng...@googlegroups.com.
To unsubscribe from this group, send email to 
google-appengine+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/google-appengine?hl=en.

[google-appengine] Re: Request was aborted after waiting too long to attempt to service your request.

[sahid]

up

On Oct 4, 10:51 am, sahid sahid.ferdja...@gmail.com wrote:
 Hello,

 I have see my warning log and i have a multiple of

 
 Request was aborted after waiting too long to attempt to service your
 request.
 This may happen sporadically when the App Engine serving cluster is
 under unexpectedly high or uneven load.
 If you see this message frequently, please contact the App Engine
 team.
 

 This exception comes from different paths.
 So i contact the App Engin team...

 APPID: devel-inchallah

 Cordialy,
 Sahid

-- 
You received this message because you are subscribed to the Google Groups 
Google App Engine group.
To post to this group, send email to google-appeng...@googlegroups.com.
To unsubscribe from this group, send email to 
google-appengine+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/google-appengine?hl=en.

Re: [google-appengine] Re: Request was aborted after waiting too long to attempt to service your request.

[andy stevko]

Hello Sahid,
You might want to read/star this issue
http://code.google.com/p/googleappengine/issues/detail?id=2396q=waiting%20too%20longcolspec=ID%20Type%20Status%20Priority%20Stars%20Owner%20Summary%20Log%20Component
--Stevko

On Tue, Oct 5, 2010 at 10:26 AM, sahid sahid.ferdja...@gmail.com wrote:

 up

 On Oct 4, 10:51 am, sahid sahid.ferdja...@gmail.com wrote:
  Hello,
 
  I have see my warning log and i have a multiple of
 
  
  Request was aborted after waiting too long to attempt to service your
  request.
  This may happen sporadically when the App Engine serving cluster is
  under unexpectedly high or uneven load.
  If you see this message frequently, please contact the App Engine
  team.
  
 
  This exception comes from different paths.
  So i contact the App Engin team...
 
  APPID: devel-inchallah
 
  Cordialy,
  Sahid

 --
 You received this message because you are subscribed to the Google Groups
 Google App Engine group.
 To post to this group, send email to google-appeng...@googlegroups.com.
 To unsubscribe from this group, send email to
 google-appengine+unsubscr...@googlegroups.comgoogle-appengine%2bunsubscr...@googlegroups.com
 .
 For more options, visit this group at
 http://groups.google.com/group/google-appengine?hl=en.



-- 
You received this message because you are subscribed to the Google Groups 
Google App Engine group.
To post to this group, send email to google-appeng...@googlegroups.com.
To unsubscribe from this group, send email to 
google-appengine+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/google-appengine?hl=en.

Re: [google-appengine] Re: Request was aborted after waiting too long to attempt to service your request

[Eduardo Perrino]

My cron runs every minute because it is the minimal period that gae
supports.



2010/6/16 Tristan tristan.slomin...@gmail.com

 From my understanding this error happens when a request hits an
 application instance but is put on a queue and becomes stale before
 other requests in front of it get out of the way and execute.

 Doesn't your cron job have to fire every second in order to keep the
 application alive? I thought that 1 request per second is the keep-
 alive boundary. It's somewhere around there. How often does your cron
 execute?

 On Jun 16, 5:51 am, Eduardo Perrino eduardo.perr...@gmail.com wrote:
  I need help my application show the next error:
 
  Request was aborted after waiting too long to attempt to service your
  request. This may happen sporadically when the App Engine serving
  cluster is under unexpectedly high or uneven load. If you see this
  message frequently, please contact the App Engine team.
 
  I created a cron job to keep alive the application, but the error
  persits, i need help to fix it.
 
  Thanks

 --
 You received this message because you are subscribed to the Google Groups
 Google App Engine group.
 To post to this group, send email to google-appeng...@googlegroups.com.
 To unsubscribe from this group, send email to
 google-appengine+unsubscr...@googlegroups.comgoogle-appengine%2bunsubscr...@googlegroups.com
 .
 For more options, visit this group at
 http://groups.google.com/group/google-appengine?hl=en.



-- 
You received this message because you are subscribed to the Google Groups 
Google App Engine group.
To post to this group, send email to google-appeng...@googlegroups.com.
To unsubscribe from this group, send email to 
google-appengine+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/google-appengine?hl=en.

[google-appengine] Re: Request was aborted after waiting too long to attempt to service your request

[Tristan]

How are you keeping the application alive by running a job every
minute? Are you queueing tasks to run every second?

On Jun 17, 2:17 am, Eduardo Perrino eduardo.perr...@gmail.com wrote:
 My cron runs every minute because it is the minimal period that gae
 supports.

 2010/6/16 Tristan tristan.slomin...@gmail.com



  From my understanding this error happens when a request hits an
  application instance but is put on a queue and becomes stale before
  other requests in front of it get out of the way and execute.

  Doesn't your cron job have to fire every second in order to keep the
  application alive? I thought that 1 request per second is the keep-
  alive boundary. It's somewhere around there. How often does your cron
  execute?

  On Jun 16, 5:51 am, Eduardo Perrino eduardo.perr...@gmail.com wrote:
   I need help my application show the next error:

   Request was aborted after waiting too long to attempt to service your
   request. This may happen sporadically when the App Engine serving
   cluster is under unexpectedly high or uneven load. If you see this
   message frequently, please contact the App Engine team.

   I created a cron job to keep alive the application, but the error
   persits, i need help to fix it.

   Thanks

  --
  You received this message because you are subscribed to the Google Groups
  Google App Engine group.
  To post to this group, send email to google-appeng...@googlegroups.com.
  To unsubscribe from this group, send email to
  google-appengine+unsubscr...@googlegroups.comgoogle-appengine%2Bunsubscrib 
  e...@googlegroups.com
  .
  For more options, visit this group at
 http://groups.google.com/group/google-appengine?hl=en.

-- 
You received this message because you are subscribed to the Google Groups 
Google App Engine group.
To post to this group, send email to google-appeng...@googlegroups.com.
To unsubscribe from this group, send email to 
google-appengine+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/google-appengine?hl=en.

[google-appengine] Re: Request was aborted after waiting too long to attempt to service your request

[Tristan]

From my understanding this error happens when a request hits an
application instance but is put on a queue and becomes stale before
other requests in front of it get out of the way and execute.

Doesn't your cron job have to fire every second in order to keep the
application alive? I thought that 1 request per second is the keep-
alive boundary. It's somewhere around there. How often does your cron
execute?

On Jun 16, 5:51 am, Eduardo Perrino eduardo.perr...@gmail.com wrote:
 I need help my application show the next error:

 Request was aborted after waiting too long to attempt to service your
 request. This may happen sporadically when the App Engine serving
 cluster is under unexpectedly high or uneven load. If you see this
 message frequently, please contact the App Engine team.

 I created a cron job to keep alive the application, but the error
 persits, i need help to fix it.

 Thanks

-- 
You received this message because you are subscribed to the Google Groups 
Google App Engine group.
To post to this group, send email to google-appeng...@googlegroups.com.
To unsubscribe from this group, send email to 
google-appengine+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/google-appengine?hl=en.