[google-appengine] Re: Request was aborted after waiting too long...

[bsb]

See my post on the exact same topic earlier today, too...

On May 5, 10:21 am, Mikkel Krautz  wrote:
> Hi,
>
> My app at alsmicdk.appspot.com has been getting the following 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.
>
> for the last couple of days now.  All requests for dynamic pages (i.e.
> script handlers), are getting the error. I'm on the Python runtime,
> BTW.
>
> I've tried to determine if anything's wrong on the app side of things
> (if certain API calls were causing the long request time) by uploading
> a new version of the app ('recovery'), but even simple request
> handlers that make no API calls are failing.
>
> The app is, in its usual condition, set up to only allow for HTTPS
> connections (secure: always). I figured this might be the cause of the
> long request times, but I've also tried to change it to (secure:
> optional) in my 'recovery' version to no avail.
>
> Any help?
>
> Mikkel
>
> --
> 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 
> athttp://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"

[bsb]

I also get the same error with cron jobs in another app of mine. This
has only started happening recently. Can someone @ Google please take
a look at this?

On May 5, 10:18 am, Benjamin Schuster-Böckler 
wrote:
> I'm getting loads of these. It's ok with the deferred tasks, as they are 
> rescheduled, but the cron jobs (to be run every 10min) just don't run if this 
> happens, causing unpredictable behaviour of my app. Effectually, the cron 
> only runs eery few hours, because most of the time, this error occurs. What 
> can I do to fix this? Do I really need to have a dummy task to constantly 
> hammer instances so the app stays loaded?
>
> Thanks in advance,
> Ben
>
> --
> 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 
> athttp://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"

[mkmanning]

One of my apps started getting this yesterday and the problem
continued all day, and is still there this a.m. This is happening any
time you visit the app. The error log for "/" shows:

"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 started after my app had been up and running for months, with no
changes; worked the day before, then dead.

Nothing in the system status shows what the cause may be or what (if
anything) is being done about this.

On May 5, 12:56 pm, bsb  wrote:
> I also get the same error with cron jobs in another app of mine. This
> has only started happening recently. Can someone @ Google please take
> a look at this?
>
> On May 5, 10:18 am, Benjamin Schuster-Böckler 
> wrote:
>
> > I'm getting loads of these. It's ok with the deferred tasks, as they are 
> > rescheduled, but the cron jobs (to be run every 10min) just don't run if 
> > this happens, causing unpredictable behaviour of my app. Effectually, the 
> > cron only runs eery few hours, because most of the time, this error occurs. 
> > What can I do to fix this? Do I really need to have a dummy task to 
> > constantly hammer instances so the app stays loaded?
>
> > Thanks in advance,
> > Ben
>
> > --
> > 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 
> > athttp://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 
> athttp://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"

[bFlood]

my task queue is filled with these today. each task had been paired
back to 20 small entity puts.



On May 6, 11:42 am, mkmanning  wrote:
> One of my apps started getting this yesterday and the problem
> continued all day, and is still there this a.m. This is happening any
> time you visit the app. The error log for "/" shows:
>
> "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 started after my app had been up and running for months, with no
> changes; worked the day before, then dead.
>
> Nothing in the system status shows what the cause may be or what (if
> anything) is being done about this.
>
> On May 5, 12:56 pm, bsb  wrote:
>
>
>
>
>
> > I also get the same error with cron jobs in another app of mine. This
> > has only started happening recently. Can someone @ Google please take
> > a look at this?
>
> > On May 5, 10:18 am, Benjamin Schuster-Böckler 
> > wrote:
>
> > > I'm getting loads of these. It's ok with the deferred tasks, as they are 
> > > rescheduled, but the cron jobs (to be run every 10min) just don't run if 
> > > this happens, causing unpredictable behaviour of my app. Effectually, the 
> > > cron only runs eery few hours, because most of the time, this error 
> > > occurs. What can I do to fix this? Do I really need to have a dummy task 
> > > to constantly hammer instances so the app stays loaded?
>
> > > Thanks in advance,
> > > Ben
>
> > > --
> > > 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 
> > > athttp://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 
> > athttp://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 
> athttp://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"

[bsb]

And for me, it's magically working flawlessly again today. Google, did
you do something? That would be good. If you didn't, it means the
service is extremely unreliable: That'd be really bad...

Ben

On May 6, 8:02 pm, Joshua Smith  wrote:
> +1  Here is my error:
>
> 05-06 11:00AM 46.656 / 500 10544ms 0cpu_ms 0kb Mozilla/5.0 (Macintosh; U; 
> Intel Mac OS X 10_6_3; en-us) AppleWebKit/531.22.7 (KHTML, like Gecko) 
> Version/4.0.5 Safari/531.22.7,gzip(gfe),gzip(gfe)
> 216.230.77.82 - - [06/May/2010:11:00:57 -0700] "GET / HTTP/1.1" 500 0 - 
> "Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10_6_3; en-us) 
> AppleWebKit/531.22.7 (KHTML, like Gecko) Version/4.0.5 
> Safari/531.22.7,gzip(gfe),gzip(gfe)" "fix3dpdf.v-central.com"
> W05-06 11:00AM 57.200
> 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.
>
> On May 6, 2010, at 12:53 PM, bFlood wrote:
>
>
>
>
>
> > my task queue is filled with these today. each task had been paired
> > back to 20 small entity puts.
>
> > On May 6, 11:42 am, mkmanning  wrote:
> >> One of my apps started getting this yesterday and the problem
> >> continued all day, and is still there this a.m. This is happening any
> >> time you visit the app. The error log for "/" shows:
>
> >> "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 started after my app had been up and running for months, with no
> >> changes; worked the day before, then dead.
>
> >> Nothing in the system status shows what the cause may be or what (if
> >> anything) is being done about this.
>
> >> On May 5, 12:56 pm, bsb  wrote:
>
> >>> I also get the same error with cron jobs in another app of mine. This
> >>> has only started happening recently. Can someone @ Google please take
> >>> a look at this?
>
> >>> On May 5, 10:18 am, Benjamin Schuster-Böckler 
> >>> wrote:
>
>  I'm getting loads of these. It's ok with the deferred tasks, as they are 
>  rescheduled, but the cron jobs (to be run every 10min) just don't run if 
>  this happens, causing unpredictable behaviour of my app. Effectually, 
>  the cron only runs eery few hours, because most of the time, this error 
>  occurs. What can I do to fix this? Do I really need to have a dummy task 
>  to constantly hammer instances so the app stays loaded?
>
>  Thanks in advance,
>  Ben
>
>  --
>  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 
>  athttp://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 
> >>> athttp://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 
> >> athttp://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 
> > athttp://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 
> athttp://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-app

[google-appengine] Re: "Request was aborted after waiting too long"

[Millisecond]

Odd, our app had gotten to a point where it was working pretty well
until this.

Since maintenance yesterday it's been all over the place, not even
sure how many errors it's throwing, the counters keep resetting.
Sometimes on their own, and once on deploying a new version with
1.3.3.1.  But about 500 errors in the last 15 minutes.

App id: noticeorange

-C

On May 6, 12:03 pm, bsb  wrote:
> And for me, it's magically working flawlessly again today. Google, did
> you do something? That would be good. If you didn't, it means the
> service is extremely unreliable: That'd be really bad...
>
> Ben
>
> On May 6, 8:02 pm, Joshua Smith  wrote:
>
>
>
>
>
> > +1  Here is my error:
>
> > 05-06 11:00AM 46.656 / 500 10544ms 0cpu_ms 0kb Mozilla/5.0 (Macintosh; U; 
> > Intel Mac OS X 10_6_3; en-us) AppleWebKit/531.22.7 (KHTML, like Gecko) 
> > Version/4.0.5 Safari/531.22.7,gzip(gfe),gzip(gfe)
> > 216.230.77.82 - - [06/May/2010:11:00:57 -0700] "GET / HTTP/1.1" 500 0 - 
> > "Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10_6_3; en-us) 
> > AppleWebKit/531.22.7 (KHTML, like Gecko) Version/4.0.5 
> > Safari/531.22.7,gzip(gfe),gzip(gfe)" "fix3dpdf.v-central.com"
> > W05-06 11:00AM 57.200
> > 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.
>
> > On May 6, 2010, at 12:53 PM, bFlood wrote:
>
> > > my task queue is filled with these today. each task had been paired
> > > back to 20 small entity puts.
>
> > > On May 6, 11:42 am, mkmanning  wrote:
> > >> One of my apps started getting this yesterday and the problem
> > >> continued all day, and is still there this a.m. This is happening any
> > >> time you visit the app. The error log for "/" shows:
>
> > >> "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 started after my app had been up and running for months, with no
> > >> changes; worked the day before, then dead.
>
> > >> Nothing in the system status shows what the cause may be or what (if
> > >> anything) is being done about this.
>
> > >> On May 5, 12:56 pm, bsb  wrote:
>
> > >>> I also get the same error with cron jobs in another app of mine. This
> > >>> has only started happening recently. Can someone @ Google please take
> > >>> a look at this?
>
> > >>> On May 5, 10:18 am, Benjamin Schuster-Böckler 
> > >>> wrote:
>
> >  I'm getting loads of these. It's ok with the deferred tasks, as they 
> >  are rescheduled, but the cron jobs (to be run every 10min) just don't 
> >  run if this happens, causing unpredictable behaviour of my app. 
> >  Effectually, the cron only runs eery few hours, because most of the 
> >  time, this error occurs. What can I do to fix this? Do I really need 
> >  to have a dummy task to constantly hammer instances so the app stays 
> >  loaded?
>
> >  Thanks in advance,
> >  Ben
>
> >  --
> >  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 
> >  athttp://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 
> > >>> athttp://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 
> > >> athttp://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 
> > > athttp://groups.google.com/group/google-appengine?hl=en.
>
> > --
> > You received this message because you are

[google-appengine] Re: Request was aborted after waiting too long

[Jan Z/ Hapara]

What is the average response time from your app for normal requests?

If it is > 1000 msec, the GAE appears to become reluctant to start up
new VM's for you, the result being that requests queue up, and after
some period in the queue, are deemed "stale" and get kicked with this
error.

Want to test this assumption?  Flood your app with no-op requests that
don't do anything (use a URL no one would normally use, and just
return from the GET call).  If you have enough of these (simplest no-
op returns in < 50 msec), the math shifts your average to below 1000
msec, and presto.

It's a stupid solution to what's either an outright bug or an
overzealous  resource manager behind GAE, but it sure seems to cure
these.

J

On Sep 15, 4:46 am, David  wrote:
> I am seeing the mesage below frequently on my application.  The
> application ID is word-play.  It seems to have started happening in
> the past day or two, but before that I never saw it.  It looks like it
> waits for 10 seconds and then times out without using any cpu_ms.
> This is causing problems.  It says to "contact the App Engine team".
> Where/how do I do that?
>
> Thanks,
> David
>
> #0.0.0.0 - xyz [14/Sep/2010:09:04:06 -0700] "GET /play?
> p=111&g=407211&m=e,13,6/d,13,7 HTTP/1.1" 500 0 - "Xxx/1.0(Android
> 2.2),gzip(gfe)" "word-play.appspot.com:80" ms=10158 cpu_ms=0
> api_cpu_ms=0 cpm_usd=0.63
>
> #W 09-14 09:04AM 06.828
>
> 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.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...

[Mark]

I am using BlazeDS - a remoting service for Flex.  I guess it takes a
while to initialize - although not sure why it is slow to init only a
small %age of the time - you would think it'd either always fail or
always succeed.

On Dec 2, 11:33 am, "Ikai L (Google)"  wrote:
> What are you doing on application startup that may be expensive?
>
>
>
> On Tue, Dec 1, 2009 at 4:04 PM, Mark  wrote:
> > Hi,
>
> >  Could someone please help me?  I have a relatively simple app - but
> > I am seeing that around 5% of the time, my app fails with error
> > 'Request was aborted after waiting too long to attempt to service your
> > request. Most likely, this indicates that you have reached your
> > simultaneous active request limit. This is almost always due to
> > excessively high latency in your app. '
>
> >  This only happens if the application has not been in use for a few
> > minutes.  I can refresh the web page, and my app always works
> > immediately.  So I guess the problem is happening when GAE cycles my
> > app out and then tries to wake it back up.
>
> >  Does anyone have any tips to get around this error?  Is it caused
> > because my app is somehow too slow to initialize?
>
> >  My appid is mayihelpyoucam
>
> > cheers
>
> > Mark
>
> > --
>
> > 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.
>
> --
> Ikai Lan
> Developer Programs Engineer, Google App Engine

--

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

[Nick (Cloud Platform Support)]

Hi Mary,

If you were affected by an outage or temporary issue, it's not really 
possible to preempt such things, and the best advice for a programmer would 
be to build redundancy and exception-handling and good monitoring into your 
app. If you believe you've been affected by an outage which violates the 
platform 
SLA , you should get in 
contact with Billing to determine if you're eligible for any kind of 
refund. 

As to your specific technical issue, I'm unable to provide insight into 
that, and in order to get more specific insight, you'd need to open a 
support ticket . 

If I understand your text correctly, you were using a manual scaling 
application and calls to create new instances using the modules service 
were failing. If you had any error output visible in the logs for your app 
at this time, that would be helpful in determining what went wrong. 

At any time, if you think you've been affected by an intermittent issue on 
the platform, you should make an issue report to the public issue tracker 
 as soon as 
possible explaining the issue, the app id, and the time-frame in which the 
incident occurred, so that we can potentially look into the logs for your 
application during the time-frame and find the cause. This is the best way 
to determine what went wrong short of reading your own logs in the case 
that it was simply a cause within your application's code.

Regards,

Nick

On Monday, August 10, 2015 at 8:11:59 AM UTC-4, Мария Кокаия wrote:
>
> In the period from 27 to 29 May Create Dynamic Instance did not finish the 
> job within a specified platform time.
>
> 1). The reasons why this happens are unknown to us. Is it possible to 
> learn more about the mechanics of creating instances?
> 2). How can we protect the service from such behavior in the future?
>
> Thanks,
> Mary
>

-- 
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/39964254-a0b0-4c3f-af84-39ad4eab4b46%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[google-appengine] Re: Request was aborted after waiting too long

[Dimitri Adamou]

If you are using Front-End instances, they can only last 60 seconds, you 
would need to create a module using Backend Instances for your heavier 
traffic as they can run up to 10 minutes per request and generally if you 
are having heavier tasks it is better to put them onto a backend instance 
and split them away from the main front-end traffic so that users will not 
feel the pinch at all.

On Monday, August 10, 2015 at 10:11:59 PM UTC+10, Мария Кокаия wrote:
>
> In the period from 27 to 29 May Create Dynamic Instance did not finish the 
> job within a specified platform time.
>
> 1). The reasons why this happens are unknown to us. Is it possible to 
> learn more about the mechanics of creating instances?
> 2). How can we protect the service from such behavior in the future?
>
> Thanks,
> Mary
>

-- 
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/08ed1c46-fe0b-45a0-ae7f-086566a36536%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [google-appengine] Re: "Request was aborted after waiting too long"

[Joshua Smith]

+1  Here is my error:

05-06 11:00AM 46.656 / 500 10544ms 0cpu_ms 0kb Mozilla/5.0 (Macintosh; U; Intel 
Mac OS X 10_6_3; en-us) AppleWebKit/531.22.7 (KHTML, like Gecko) Version/4.0.5 
Safari/531.22.7,gzip(gfe),gzip(gfe)
216.230.77.82 - - [06/May/2010:11:00:57 -0700] "GET / HTTP/1.1" 500 0 - 
"Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10_6_3; en-us) AppleWebKit/531.22.7 
(KHTML, like Gecko) Version/4.0.5 Safari/531.22.7,gzip(gfe),gzip(gfe)" 
"fix3dpdf.v-central.com"
W05-06 11:00AM 57.200
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.

On May 6, 2010, at 12:53 PM, bFlood wrote:

> my task queue is filled with these today. each task had been paired
> back to 20 small entity puts.
> 
> 
> 
> On May 6, 11:42 am, mkmanning  wrote:
>> One of my apps started getting this yesterday and the problem
>> continued all day, and is still there this a.m. This is happening any
>> time you visit the app. The error log for "/" shows:
>> 
>> "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 started after my app had been up and running for months, with no
>> changes; worked the day before, then dead.
>> 
>> Nothing in the system status shows what the cause may be or what (if
>> anything) is being done about this.
>> 
>> On May 5, 12:56 pm, bsb  wrote:
>> 
>> 
>> 
>> 
>> 
>>> I also get the same error with cron jobs in another app of mine. This
>>> has only started happening recently. Can someone @ Google please take
>>> a look at this?
>> 
>>> On May 5, 10:18 am, Benjamin Schuster-Böckler 
>>> wrote:
>> 
 I'm getting loads of these. It's ok with the deferred tasks, as they are 
 rescheduled, but the cron jobs (to be run every 10min) just don't run if 
 this happens, causing unpredictable behaviour of my app. Effectually, the 
 cron only runs eery few hours, because most of the time, this error 
 occurs. What can I do to fix this? Do I really need to have a dummy task 
 to constantly hammer instances so the app stays loaded?
>> 
 Thanks in advance,
 Ben
>> 
 --
 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 
 athttp://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 
>>> athttp://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 
>> athttp://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.
> 

-- 
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

[Ikai Lan (Google)]

It's not a bug - it's something we've stated before. App Engine's
infrastructure will favor lots of small requests over large requests for
user facing requests.

The reason your suggestion probably wouldn't work well is that the
proportion of requests that must be fast must be high. This means that if
the original poster already has a requirement for many long running
requests, that he would need many multiples of that number to be auto-scaled
up. It'd be a very costly way of doing something where an alternative
solution exists using Task Queues or cron tasks.

It's far more likely the issue is being caused by our latency spikes
described here:

http://groups.google.com/group/google-appengine-downtime-notify/browse_thread/thread/9cf3b0cafdd6c235

On Wed, Sep 15, 2010 at 4:32 AM, Jan Z/ Hapara wrote:

> What is the average response time from your app for normal requests?
>
> If it is > 1000 msec, the GAE appears to become reluctant to start up
> new VM's for you, the result being that requests queue up, and after
> some period in the queue, are deemed "stale" and get kicked with this
> error.
>
> Want to test this assumption?  Flood your app with no-op requests that
> don't do anything (use a URL no one would normally use, and just
> return from the GET call).  If you have enough of these (simplest no-
> op returns in < 50 msec), the math shifts your average to below 1000
> msec, and presto.
>
> It's a stupid solution to what's either an outright bug or an
> overzealous  resource manager behind GAE, but it sure seems to cure
> these.
>
> J
>
> On Sep 15, 4:46 am, David  wrote:
> > I am seeing the mesage below frequently on my application.  The
> > application ID is word-play.  It seems to have started happening in
> > the past day or two, but before that I never saw it.  It looks like it
> > waits for 10 seconds and then times out without using any cpu_ms.
> > This is causing problems.  It says to "contact the App Engine team".
> > Where/how do I do that?
> >
> > Thanks,
> > David
> >
> > #0.0.0.0 - xyz [14/Sep/2010:09:04:06 -0700] "GET /play?
> > p=111&g=407211&m=e,13,6/d,13,7 HTTP/1.1" 500 0 - "Xxx/1.0(Android
> > 2.2),gzip(gfe)" "word-play.appspot.com:80" ms=10158 cpu_ms=0
> > api_cpu_ms=0 cpm_usd=0.63
> >
> > #W 09-14 09:04AM 06.828
> >
> > 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.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...

[Ikai L (Google)]

Mark,

Yes, it should take roughly the same amount of time. Do you notice that it's
more likely to happen at certain times of the day rather than others?

On Wed, Dec 2, 2009 at 12:49 PM, Mark  wrote:

> I am using BlazeDS - a remoting service for Flex.  I guess it takes a
> while to initialize - although not sure why it is slow to init only a
> small %age of the time - you would think it'd either always fail or
> always succeed.
>
> On Dec 2, 11:33 am, "Ikai L (Google)"  wrote:
> > What are you doing on application startup that may be expensive?
> >
> >
> >
> > On Tue, Dec 1, 2009 at 4:04 PM, Mark  wrote:
> > > Hi,
> >
> > >  Could someone please help me?  I have a relatively simple app - but
> > > I am seeing that around 5% of the time, my app fails with error
> > > 'Request was aborted after waiting too long to attempt to service your
> > > request. Most likely, this indicates that you have reached your
> > > simultaneous active request limit. This is almost always due to
> > > excessively high latency in your app. '
> >
> > >  This only happens if the application has not been in use for a few
> > > minutes.  I can refresh the web page, and my app always works
> > > immediately.  So I guess the problem is happening when GAE cycles my
> > > app out and then tries to wake it back up.
> >
> > >  Does anyone have any tips to get around this error?  Is it caused
> > > because my app is somehow too slow to initialize?
> >
> > >  My appid is mayihelpyoucam
> >
> > > cheers
> >
> > > Mark
> >
> > > --
> >
> > > 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.com
> 
> >
> > > .
> > > For more options, visit this group at
> > >http://groups.google.com/group/google-appengine?hl=en.
> >
> > --
> > Ikai Lan
> > Developer Programs Engineer, Google App Engine
>
> --
>
> 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.
>
>
>


-- 
Ikai Lan
Developer Programs Engineer, Google App Engine

--

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  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.

[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  wrote:
> My cron runs every minute because it is the minimal period that gae
> supports.
>
> 2010/6/16 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  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 > 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.

[sahid]

up

On Oct 4, 10:51 am, sahid  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.

[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)" 
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
> wrote:
>
> > 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.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" followed by random DeadlineExceededError on import.

[Dave Peck]

Hi Ikai,

The app id is "citygoround".

We had a number of stretches of "badness" this morning. An example
stretch:

6:07AM 33.867 ("Request was aborted...")
6:07AM 49.672 through 7:12AM 24.470 ("DeadlineExceededError" and/or
"ImproperlyConfiguredError" -- looks like it depends on which imports
fail.)

And another:

8:17AM 37.620 ("Request was aborted...")
8:17AM 54.348 through 8:46AM 51.478 ("DeadlineExceededError" and/or
"ImproperlyConfiguredError")

One last thing: the app is open source. If it helps, you can find the
exact code that we're running in production at:

http://github.com/davepeck/CityGoRound/

The screenshot handler in question is found in ./citygoround/views/
app.py Line 115.

Cheers,
Dave


On Dec 14, 1:32 pm, "Ikai L (Google)"  wrote:
> Do you see that it's consistent at the same times? What's your application
> ID? I'll look into it.
>
>
>
>
>
> On Mon, Dec 14, 2009 at 11:28 AM, Dave Peck  wrote:
> > Hello,
>
> > I have an app (citygoround.org) that, especially in the morning, often
> > has 10-15 minutes of outright downtime due to server errors.
>
> > Looking into it, I see that right before the downtime starts, a few
> > requests log the following warning message:
>
> >    > Request was aborted after waiting too long to attempt to service
> > your request.
> >    > Most likely, this indicates that you have reached your
> > simultaneous dynamic request limit.
>
> > I'm certainly not over my limit, but I can believe that the request in
> > question could take a while. (I'll get to the details of that request
> > in a moment.)
>
> > Immediately after these warnings, my app has a large amount of time
> > (10+ minutes) where *all requests* -- no matter how unthreatening --
> > raise a DeadlineExceededError. Usually this is raised during the
> > import of an innocuous module like "re" or "time" or perhaps a Django
> > 1.1 module. (We use use_library.)
>
> > My best theory at the moment is that:
>
> > 1. It's a cold start, so nothing is cached.
> > 2. App Engine encounters the high latency request and bails.
> > 3. We probably inadvertently catch the DeadlineExceededError, so the
> > runtime doesn't clean up properly.
> > 4. Future requests are left in a busted state.
>
> > Does this sound at all reasonable? I see a few related issues (2396,
> > 2266, and 1409) but no firm/completely clear discussion of what's
> > happening in any of them.
>
> > Thanks,
> > Dave
>
> > PS:
>
> > The specifics about our high latency request are *not* strictly
> > relevant to the larger problem I'm having, but I will include them
> > because I have a second "side" question to ask about it.
>
> > The "high latency" request is serving an image. Our app lets users
> > upload images and we store them in the data store. When serving an
> > image, our handler:
>
> > 1. Checks to see if the bytes for the image are in memcache, and if so
> > returns them immediately.
> > 2. Otherwise grabs the image from the datastore, and if it is smaller
> > than 64K, adds the bytes to the memcache
> > 3. Returns the result
>
> > I'm wondering if using memcache in this way is a smart idea -- it may
> > very well be the cause of our latency issues. It's hard to tell.
>
> > Alternatively, the issue could be: we have a page that shows a large
> > number (~100) of such images. If someone requests this page, we may
> > have a lot of simultaneous image-producing requests happening at the
> > same time. Perhaps _this_ is the root cause of the original "Request
> > was aborted" issue?
>
> > Just not sure here...
>
> > --
>
> > 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 > e...@googlegroups.com>
> > .
> > For more options, visit this group at
> >http://groups.google.com/group/google-appengine?hl=en.
>
> --
> Ikai Lan
> Developer Programs Engineer, Google App Engine

--

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" followed by random DeadlineExceededError on import.

[Jason C]

Ikai,

We see daily DeadlineExceededErrors on app id 'steprep' from 6.30am to
7.30am (log time).

Can you look into that as well?

Thanks,
j

On Dec 14, 3:32 pm, "Ikai L (Google)"  wrote:
> Do you see that it's consistent at the same times? What's your application
> ID? I'll look into it.
>
>
>
>
>
> On Mon, Dec 14, 2009 at 11:28 AM, Dave Peck  wrote:
> > Hello,
>
> > I have an app (citygoround.org) that, especially in the morning, often
> > has 10-15 minutes of outright downtime due to server errors.
>
> > Looking into it, I see that right before the downtime starts, a few
> > requests log the following warning message:
>
> >    > Request was aborted after waiting too long to attempt to service
> > your request.
> >    > Most likely, this indicates that you have reached your
> > simultaneous dynamic request limit.
>
> > I'm certainly not over my limit, but I can believe that the request in
> > question could take a while. (I'll get to the details of that request
> > in a moment.)
>
> > Immediately after these warnings, my app has a large amount of time
> > (10+ minutes) where *all requests* -- no matter how unthreatening --
> > raise a DeadlineExceededError. Usually this is raised during the
> > import of an innocuous module like "re" or "time" or perhaps a Django
> > 1.1 module. (We use use_library.)
>
> > My best theory at the moment is that:
>
> > 1. It's a cold start, so nothing is cached.
> > 2. App Engine encounters the high latency request and bails.
> > 3. We probably inadvertently catch the DeadlineExceededError, so the
> > runtime doesn't clean up properly.
> > 4. Future requests are left in a busted state.
>
> > Does this sound at all reasonable? I see a few related issues (2396,
> > 2266, and 1409) but no firm/completely clear discussion of what's
> > happening in any of them.
>
> > Thanks,
> > Dave
>
> > PS:
>
> > The specifics about our high latency request are *not* strictly
> > relevant to the larger problem I'm having, but I will include them
> > because I have a second "side" question to ask about it.
>
> > The "high latency" request is serving an image. Our app lets users
> > upload images and we store them in the data store. When serving an
> > image, our handler:
>
> > 1. Checks to see if the bytes for the image are in memcache, and if so
> > returns them immediately.
> > 2. Otherwise grabs the image from the datastore, and if it is smaller
> > than 64K, adds the bytes to the memcache
> > 3. Returns the result
>
> > I'm wondering if using memcache in this way is a smart idea -- it may
> > very well be the cause of our latency issues. It's hard to tell.
>
> > Alternatively, the issue could be: we have a page that shows a large
> > number (~100) of such images. If someone requests this page, we may
> > have a lot of simultaneous image-producing requests happening at the
> > same time. Perhaps _this_ is the root cause of the original "Request
> > was aborted" issue?
>
> > Just not sure here...
>
> > --
>
> > 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 > e...@googlegroups.com>
> > .
> > For more options, visit this group at
> >http://groups.google.com/group/google-appengine?hl=en.
>
> --
> Ikai Lan
> Developer Programs Engineer, Google App Engine

--

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" followed by random DeadlineExceededError on import.

[Dave Peck]

Hi Ikai,

Any further details on your end? I get the feeling we're not the only
ones, and we've experienced very serious downtime in the last ~48
hours.

This is a critical issue for us to resolve, but at the same time we
lack key pieces of data that would help us solve it on our own...

Thanks,
Dave

On Dec 15, 9:14 am, Jason C  wrote:
> Ikai,
>
> We see daily DeadlineExceededErrors on app id 'steprep' from 6.30am to
> 7.30am (log time).
>
> Can you look into that as well?
>
> Thanks,
> j
>
> On Dec 14, 3:32 pm, "Ikai L (Google)"  wrote:
>
>
>
> > Do you see that it's consistent at the same times? What's your application
> > ID? I'll look into it.
>
> > On Mon, Dec 14, 2009 at 11:28 AM, Dave Peck  wrote:
> > > Hello,
>
> > > I have an app (citygoround.org) that, especially in the morning, often
> > > has 10-15 minutes of outright downtime due to server errors.
>
> > > Looking into it, I see that right before the downtime starts, a few
> > > requests log the following warning message:
>
> > >    > Request was aborted after waiting too long to attempt to service
> > > your request.
> > >    > Most likely, this indicates that you have reached your
> > > simultaneous dynamic request limit.
>
> > > I'm certainly not over my limit, but I can believe that the request in
> > > question could take a while. (I'll get to the details of that request
> > > in a moment.)
>
> > > Immediately after these warnings, my app has a large amount of time
> > > (10+ minutes) where *all requests* -- no matter how unthreatening --
> > > raise a DeadlineExceededError. Usually this is raised during the
> > > import of an innocuous module like "re" or "time" or perhaps a Django
> > > 1.1 module. (We use use_library.)
>
> > > My best theory at the moment is that:
>
> > > 1. It's a cold start, so nothing is cached.
> > > 2. App Engine encounters the high latency request and bails.
> > > 3. We probably inadvertently catch the DeadlineExceededError, so the
> > > runtime doesn't clean up properly.
> > > 4. Future requests are left in a busted state.
>
> > > Does this sound at all reasonable? I see a few related issues (2396,
> > > 2266, and 1409) but no firm/completely clear discussion of what's
> > > happening in any of them.
>
> > > Thanks,
> > > Dave
>
> > > PS:
>
> > > The specifics about our high latency request are *not* strictly
> > > relevant to the larger problem I'm having, but I will include them
> > > because I have a second "side" question to ask about it.
>
> > > The "high latency" request is serving an image. Our app lets users
> > > upload images and we store them in the data store. When serving an
> > > image, our handler:
>
> > > 1. Checks to see if the bytes for the image are in memcache, and if so
> > > returns them immediately.
> > > 2. Otherwise grabs the image from the datastore, and if it is smaller
> > > than 64K, adds the bytes to the memcache
> > > 3. Returns the result
>
> > > I'm wondering if using memcache in this way is a smart idea -- it may
> > > very well be the cause of our latency issues. It's hard to tell.
>
> > > Alternatively, the issue could be: we have a page that shows a large
> > > number (~100) of such images. If someone requests this page, we may
> > > have a lot of simultaneous image-producing requests happening at the
> > > same time. Perhaps _this_ is the root cause of the original "Request
> > > was aborted" issue?
>
> > > Just not sure here...
>
> > > --
>
> > > 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 > >  e...@googlegroups.com>
> > > .
> > > For more options, visit this group at
> > >http://groups.google.com/group/google-appengine?hl=en.
>
> > --
> > Ikai Lan
> > Developer Programs Engineer, Google App Engine

--

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" followed by random DeadlineExceededError on import.

[Dave Peck]

Ikai,

We'll keep an eye on our app for the next ~24 hours and report back.

At what time did you make the changes to our instance? We had
substantial downtime earlier today, alas.

Can you provide any details about what sort of change was made?

Thanks,
Dave

On Dec 15, 11:26 am, "Ikai L (Google)"  wrote:
> Dave,
>
> You're correct that this is likely affecting other applications, but it's
> not a global issue. There are hotspots in the cloud that we notice are being
> especially impacted during certain times of the day. We're actively working
> on addressing these issues, but in the meantime, there are manual steps we
> can try to prevent your applications from becoming resource starved. We do
> these on a one-off basis and reserve them only for applications that seem to
> exhibit the behavior of seeing DeadlineExceeded on simple actions (not
> initial JVM startup), and at fairly predictable intervals during the day.
> I've taken these steps to try to remedy your application. Can you let us
> know if these seem to help? If not, they may indicate that something is
> going on with your application code, though that does not seem like the case
> here.
>
>
>
>
>
> On Tue, Dec 15, 2009 at 10:54 AM, Dave Peck  wrote:
> > Hi Ikai,
>
> > Any further details on your end? I get the feeling we're not the only
> > ones, and we've experienced very serious downtime in the last ~48
> > hours.
>
> > This is a critical issue for us to resolve, but at the same time we
> > lack key pieces of data that would help us solve it on our own...
>
> > Thanks,
> > Dave
>
> > On Dec 15, 9:14 am, Jason C  wrote:
> > > Ikai,
>
> > > We see daily DeadlineExceededErrors on app id 'steprep' from 6.30am to
> > > 7.30am (log time).
>
> > > Can you look into that as well?
>
> > > Thanks,
> > > j
>
> > > On Dec 14, 3:32 pm, "Ikai L (Google)"  wrote:
>
> > > > Do you see that it's consistent at the same times? What's your
> > application
> > > > ID? I'll look into it.
>
> > > > On Mon, Dec 14, 2009 at 11:28 AM, Dave Peck 
> > wrote:
> > > > > Hello,
>
> > > > > I have an app (citygoround.org) that, especially in the morning,
> > often
> > > > > has 10-15 minutes of outright downtime due to server errors.
>
> > > > > Looking into it, I see that right before the downtime starts, a few
> > > > > requests log the following warning message:
>
> > > > >    > Request was aborted after waiting too long to attempt to service
> > > > > your request.
> > > > >    > Most likely, this indicates that you have reached your
> > > > > simultaneous dynamic request limit.
>
> > > > > I'm certainly not over my limit, but I can believe that the request
> > in
> > > > > question could take a while. (I'll get to the details of that request
> > > > > in a moment.)
>
> > > > > Immediately after these warnings, my app has a large amount of time
> > > > > (10+ minutes) where *all requests* -- no matter how unthreatening --
> > > > > raise a DeadlineExceededError. Usually this is raised during the
> > > > > import of an innocuous module like "re" or "time" or perhaps a Django
> > > > > 1.1 module. (We use use_library.)
>
> > > > > My best theory at the moment is that:
>
> > > > > 1. It's a cold start, so nothing is cached.
> > > > > 2. App Engine encounters the high latency request and bails.
> > > > > 3. We probably inadvertently catch the DeadlineExceededError, so the
> > > > > runtime doesn't clean up properly.
> > > > > 4. Future requests are left in a busted state.
>
> > > > > Does this sound at all reasonable? I see a few related issues (2396,
> > > > > 2266, and 1409) but no firm/completely clear discussion of what's
> > > > > happening in any of them.
>
> > > > > Thanks,
> > > > > Dave
>
> > > > > PS:
>
> > > > > The specifics about our high latency request are *not* strictly
> > > > > relevant to the larger problem I'm having, but I will include them
> > > > > because I have a second "side" question to ask about it.
>
> > > > > The "high latency" request is serving an image. Our app lets users
> > > > > upload images and we store them in the data store. When serving an
> > > > > image, our handler:
>
> > > > > 1. Checks to see if the bytes for the image are in memcache, and if
> > so
> > > > > returns them immediately.
> > > > > 2. Otherwise grabs the image from the datastore, and if it is smaller
> > > > > than 64K, adds the bytes to the memcache
> > > > > 3. Returns the result
>
> > > > > I'm wondering if using memcache in this way is a smart idea -- it may
> > > > > very well be the cause of our latency issues. It's hard to tell.
>
> > > > > Alternatively, the issue could be: we have a page that shows a large
> > > > > number (~100) of such images. If someone requests this page, we may
> > > > > have a lot of simultaneous image-producing requests happening at the
> > > > > same time. Perhaps _this_ is the root cause of the original "Request
> > > > > was aborted" issue?
>
> > > > > Just not sure here...
>
> > > > > --
>
> > > > > You received this message be

[google-appengine] Re: "Request was aborted after waiting too long" followed by random DeadlineExceededError on import.

[Jason C]

We (steprep) still saw a set of them on Dec 16 starting 3.54am through
6.57am (log time).

j

On Dec 15, 1:56 pm, "Ikai L (Google)"  wrote:
> I made the change right before I sent the email. Let me know how it works
> for you.
>
> Jason, I also made the change to your application. Please report back after
> tomorrow if you continue to experience issues.
>
>
>
>
>
> On Tue, Dec 15, 2009 at 11:39 AM, Dave Peck  wrote:
> > Ikai,
>
> > We'll keep an eye on our app for the next ~24 hours and report back.
>
> > At what time did you make the changes to our instance? We had
> > substantial downtime earlier today, alas.
>
> > Can you provide any details about what sort of change was made?
>
> > Thanks,
> > Dave
>
> > On Dec 15, 11:26 am, "Ikai L (Google)"  wrote:
> > > Dave,
>
> > > You're correct that this is likely affecting other applications, but it's
> > > not a global issue. There are hotspots in the cloud that we notice are
> > being
> > > especially impacted during certain times of the day. We're actively
> > working
> > > on addressing these issues, but in the meantime, there are manual steps
> > we
> > > can try to prevent your applications from becoming resource starved. We
> > do
> > > these on a one-off basis and reserve them only for applications that seem
> > to
> > > exhibit the behavior of seeing DeadlineExceeded on simple actions (not
> > > initial JVM startup), and at fairly predictable intervals during the day.
> > > I've taken these steps to try to remedy your application. Can you let us
> > > know if these seem to help? If not, they may indicate that something is
> > > going on with your application code, though that does not seem like the
> > case
> > > here.
>
> > > On Tue, Dec 15, 2009 at 10:54 AM, Dave Peck  wrote:
> > > > Hi Ikai,
>
> > > > Any further details on your end? I get the feeling we're not the only
> > > > ones, and we've experienced very serious downtime in the last ~48
> > > > hours.
>
> > > > This is a critical issue for us to resolve, but at the same time we
> > > > lack key pieces of data that would help us solve it on our own...
>
> > > > Thanks,
> > > > Dave
>
> > > > On Dec 15, 9:14 am, Jason C  wrote:
> > > > > Ikai,
>
> > > > > We see daily DeadlineExceededErrors on app id 'steprep' from 6.30am
> > to
> > > > > 7.30am (log time).
>
> > > > > Can you look into that as well?
>
> > > > > Thanks,
> > > > > j
>
> > > > > On Dec 14, 3:32 pm, "Ikai L (Google)"  wrote:
>
> > > > > > Do you see that it's consistent at the same times? What's your
> > > > application
> > > > > > ID? I'll look into it.
>
> > > > > > On Mon, Dec 14, 2009 at 11:28 AM, Dave Peck 
> > > > wrote:
> > > > > > > Hello,
>
> > > > > > > I have an app (citygoround.org) that, especially in the morning,
> > > > often
> > > > > > > has 10-15 minutes of outright downtime due to server errors.
>
> > > > > > > Looking into it, I see that right before the downtime starts, a
> > few
> > > > > > > requests log the following warning message:
>
> > > > > > >    > Request was aborted after waiting too long to attempt to
> > service
> > > > > > > your request.
> > > > > > >    > Most likely, this indicates that you have reached your
> > > > > > > simultaneous dynamic request limit.
>
> > > > > > > I'm certainly not over my limit, but I can believe that the
> > request
> > > > in
> > > > > > > question could take a while. (I'll get to the details of that
> > request
> > > > > > > in a moment.)
>
> > > > > > > Immediately after these warnings, my app has a large amount of
> > time
> > > > > > > (10+ minutes) where *all requests* -- no matter how unthreatening
> > --
> > > > > > > raise a DeadlineExceededError. Usually this is raised during the
> > > > > > > import of an innocuous module like "re" or "time" or perhaps a
> > Django
> > > > > > > 1.1 module. (We use use_library.)
>
> > > > > > > My best theory at the moment is that:
>
> > > > > > > 1. It's a cold start, so nothing is cached.
> > > > > > > 2. App Engine encounters the high latency request and bails.
> > > > > > > 3. We probably inadvertently catch the DeadlineExceededError, so
> > the
> > > > > > > runtime doesn't clean up properly.
> > > > > > > 4. Future requests are left in a busted state.
>
> > > > > > > Does this sound at all reasonable? I see a few related issues
> > (2396,
> > > > > > > 2266, and 1409) but no firm/completely clear discussion of what's
> > > > > > > happening in any of them.
>
> > > > > > > Thanks,
> > > > > > > Dave
>
> > > > > > > PS:
>
> > > > > > > The specifics about our high latency request are *not* strictly
> > > > > > > relevant to the larger problem I'm having, but I will include
> > them
> > > > > > > because I have a second "side" question to ask about it.
>
> > > > > > > The "high latency" request is serving an image. Our app lets
> > users
> > > > > > > upload images and we store them in the data store. When serving
> > an
> > > > > > > image, our handler:
>
> > > > > > > 1. Checks to see if the bytes for the image are in

[google-appengine] Re: "Request was aborted after waiting too long" followed by random DeadlineExceededError on import.

[Wesley Chun (Google)]

dave, jason,

just wanted to do a follow-up to see where things stand with your apps
now. i'm coming across a similar user issue and was wondering whether
it's the same problem or not. can you post your complete error stack
traces if you're still running into this issue? here's the issue filed
by the other user FYI, who's app seems to have few requests but each
one has high latency:

http://code.google.com/p/googleappengine/issues/detail?id=2621

if your respective apps don't suffer from this problem any more, what
did you do to resolve it or did it magically go away?

thanks,
-- wesley
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
"Core Python Programming", Prentice Hall, (c)2007,2001
"Python Fundamentals", Prentice Hall, (c)2009
   http://corepython.com

wesley.j.chun :: wesc+...@google.com
developer relations :: google app engine

-- 
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" followed by random DeadlineExceededError on import.

[Jason C]

I was under the impression that something happened internally at
Google to adjust the way that apps were balanced around machines and/
or other internal tuning.

Additionally, we run a ping every 10 seconds to keep an instance hot.
While I understand how this doesn't have much effect in a distributed
environment (though practically speaking in this case it does seem to
have a positive effect), and while I also understand how this is
"abuses" a shared resource, I'm currently afraid to turn it off.

j

On Jan 19, 8:10 pm, "Wesley Chun (Google)" 
wrote:
> dave, jason,
>
> just wanted to do a follow-up to see where things stand with your apps
> now. i'm coming across a similar user issue and was wondering whether
> it's the same problem or not. can you post your complete error stack
> traces if you're still running into this issue? here's the issue filed
> by the other user FYI, who's app seems to have few requests but each
> one has high latency:
>
> http://code.google.com/p/googleappengine/issues/detail?id=2621
>
> if your respective apps don't suffer from this problem any more, what
> did you do to resolve it or did it magically go away?
>
> thanks,
> -- wesley
> - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
> "Core Python Programming", Prentice Hall, (c)2007,2001
> "Python Fundamentals", Prentice Hall, (c)2009
>    http://corepython.com
>
> wesley.j.chun :: wesc+...@google.com
> developer relations :: google app engine
-- 
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

[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"

[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 
>
>
>
>  
>

-- 
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"

[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

['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.

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 

> 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  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.
>
>

-- 
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=2396&q=waiting%20too%20long&colspec=ID%20Type%20Status%20Priority%20Stars%20Owner%20Summary%20Log%20Component
--Stevko

On Tue, Oct 5, 2010 at 10:26 AM, sahid  wrote:

> up
>
> On Oct 4, 10:51 am, sahid  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.
>
>

-- 
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  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)" 
> 
> >
> 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
> > wrote:
> >
> > > 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.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.
>
>

-- 
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" followed by random DeadlineExceededError on import.

[Ikai L (Google)]

Dave,

You're correct that this is likely affecting other applications, but it's
not a global issue. There are hotspots in the cloud that we notice are being
especially impacted during certain times of the day. We're actively working
on addressing these issues, but in the meantime, there are manual steps we
can try to prevent your applications from becoming resource starved. We do
these on a one-off basis and reserve them only for applications that seem to
exhibit the behavior of seeing DeadlineExceeded on simple actions (not
initial JVM startup), and at fairly predictable intervals during the day.
I've taken these steps to try to remedy your application. Can you let us
know if these seem to help? If not, they may indicate that something is
going on with your application code, though that does not seem like the case
here.


On Tue, Dec 15, 2009 at 10:54 AM, Dave Peck  wrote:

> Hi Ikai,
>
> Any further details on your end? I get the feeling we're not the only
> ones, and we've experienced very serious downtime in the last ~48
> hours.
>
> This is a critical issue for us to resolve, but at the same time we
> lack key pieces of data that would help us solve it on our own...
>
> Thanks,
> Dave
>
> On Dec 15, 9:14 am, Jason C  wrote:
> > Ikai,
> >
> > We see daily DeadlineExceededErrors on app id 'steprep' from 6.30am to
> > 7.30am (log time).
> >
> > Can you look into that as well?
> >
> > Thanks,
> > j
> >
> > On Dec 14, 3:32 pm, "Ikai L (Google)"  wrote:
> >
> >
> >
> > > Do you see that it's consistent at the same times? What's your
> application
> > > ID? I'll look into it.
> >
> > > On Mon, Dec 14, 2009 at 11:28 AM, Dave Peck 
> wrote:
> > > > Hello,
> >
> > > > I have an app (citygoround.org) that, especially in the morning,
> often
> > > > has 10-15 minutes of outright downtime due to server errors.
> >
> > > > Looking into it, I see that right before the downtime starts, a few
> > > > requests log the following warning message:
> >
> > > >> Request was aborted after waiting too long to attempt to service
> > > > your request.
> > > >> Most likely, this indicates that you have reached your
> > > > simultaneous dynamic request limit.
> >
> > > > I'm certainly not over my limit, but I can believe that the request
> in
> > > > question could take a while. (I'll get to the details of that request
> > > > in a moment.)
> >
> > > > Immediately after these warnings, my app has a large amount of time
> > > > (10+ minutes) where *all requests* -- no matter how unthreatening --
> > > > raise a DeadlineExceededError. Usually this is raised during the
> > > > import of an innocuous module like "re" or "time" or perhaps a Django
> > > > 1.1 module. (We use use_library.)
> >
> > > > My best theory at the moment is that:
> >
> > > > 1. It's a cold start, so nothing is cached.
> > > > 2. App Engine encounters the high latency request and bails.
> > > > 3. We probably inadvertently catch the DeadlineExceededError, so the
> > > > runtime doesn't clean up properly.
> > > > 4. Future requests are left in a busted state.
> >
> > > > Does this sound at all reasonable? I see a few related issues (2396,
> > > > 2266, and 1409) but no firm/completely clear discussion of what's
> > > > happening in any of them.
> >
> > > > Thanks,
> > > > Dave
> >
> > > > PS:
> >
> > > > The specifics about our high latency request are *not* strictly
> > > > relevant to the larger problem I'm having, but I will include them
> > > > because I have a second "side" question to ask about it.
> >
> > > > The "high latency" request is serving an image. Our app lets users
> > > > upload images and we store them in the data store. When serving an
> > > > image, our handler:
> >
> > > > 1. Checks to see if the bytes for the image are in memcache, and if
> so
> > > > returns them immediately.
> > > > 2. Otherwise grabs the image from the datastore, and if it is smaller
> > > > than 64K, adds the bytes to the memcache
> > > > 3. Returns the result
> >
> > > > I'm wondering if using memcache in this way is a smart idea -- it may
> > > > very well be the cause of our latency issues. It's hard to tell.
> >
> > > > Alternatively, the issue could be: we have a page that shows a large
> > > > number (~100) of such images. If someone requests this page, we may
> > > > have a lot of simultaneous image-producing requests happening at the
> > > > same time. Perhaps _this_ is the root cause of the original "Request
> > > > was aborted" issue?
> >
> > > > Just not sure here...
> >
> > > > --
> >
> > > > 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 e...@googlegroups.com>
> > > > .
> > > > For more options, visit this group at
> > > >http://groups.google.com/group/google-appengine?hl=en.
> >
> > > --
> > > Ika

Re: [google-appengine] Re: "Request was aborted after waiting too long" followed by random DeadlineExceededError on import.

[Ikai L (Google)]

I made the change right before I sent the email. Let me know how it works
for you.

Jason, I also made the change to your application. Please report back after
tomorrow if you continue to experience issues.

On Tue, Dec 15, 2009 at 11:39 AM, Dave Peck  wrote:

> Ikai,
>
> We'll keep an eye on our app for the next ~24 hours and report back.
>
> At what time did you make the changes to our instance? We had
> substantial downtime earlier today, alas.
>
> Can you provide any details about what sort of change was made?
>
> Thanks,
> Dave
>
> On Dec 15, 11:26 am, "Ikai L (Google)"  wrote:
> > Dave,
> >
> > You're correct that this is likely affecting other applications, but it's
> > not a global issue. There are hotspots in the cloud that we notice are
> being
> > especially impacted during certain times of the day. We're actively
> working
> > on addressing these issues, but in the meantime, there are manual steps
> we
> > can try to prevent your applications from becoming resource starved. We
> do
> > these on a one-off basis and reserve them only for applications that seem
> to
> > exhibit the behavior of seeing DeadlineExceeded on simple actions (not
> > initial JVM startup), and at fairly predictable intervals during the day.
> > I've taken these steps to try to remedy your application. Can you let us
> > know if these seem to help? If not, they may indicate that something is
> > going on with your application code, though that does not seem like the
> case
> > here.
> >
> >
> >
> >
> >
> > On Tue, Dec 15, 2009 at 10:54 AM, Dave Peck  wrote:
> > > Hi Ikai,
> >
> > > Any further details on your end? I get the feeling we're not the only
> > > ones, and we've experienced very serious downtime in the last ~48
> > > hours.
> >
> > > This is a critical issue for us to resolve, but at the same time we
> > > lack key pieces of data that would help us solve it on our own...
> >
> > > Thanks,
> > > Dave
> >
> > > On Dec 15, 9:14 am, Jason C  wrote:
> > > > Ikai,
> >
> > > > We see daily DeadlineExceededErrors on app id 'steprep' from 6.30am
> to
> > > > 7.30am (log time).
> >
> > > > Can you look into that as well?
> >
> > > > Thanks,
> > > > j
> >
> > > > On Dec 14, 3:32 pm, "Ikai L (Google)"  wrote:
> >
> > > > > Do you see that it's consistent at the same times? What's your
> > > application
> > > > > ID? I'll look into it.
> >
> > > > > On Mon, Dec 14, 2009 at 11:28 AM, Dave Peck 
> > > wrote:
> > > > > > Hello,
> >
> > > > > > I have an app (citygoround.org) that, especially in the morning,
> > > often
> > > > > > has 10-15 minutes of outright downtime due to server errors.
> >
> > > > > > Looking into it, I see that right before the downtime starts, a
> few
> > > > > > requests log the following warning message:
> >
> > > > > >> Request was aborted after waiting too long to attempt to
> service
> > > > > > your request.
> > > > > >> Most likely, this indicates that you have reached your
> > > > > > simultaneous dynamic request limit.
> >
> > > > > > I'm certainly not over my limit, but I can believe that the
> request
> > > in
> > > > > > question could take a while. (I'll get to the details of that
> request
> > > > > > in a moment.)
> >
> > > > > > Immediately after these warnings, my app has a large amount of
> time
> > > > > > (10+ minutes) where *all requests* -- no matter how unthreatening
> --
> > > > > > raise a DeadlineExceededError. Usually this is raised during the
> > > > > > import of an innocuous module like "re" or "time" or perhaps a
> Django
> > > > > > 1.1 module. (We use use_library.)
> >
> > > > > > My best theory at the moment is that:
> >
> > > > > > 1. It's a cold start, so nothing is cached.
> > > > > > 2. App Engine encounters the high latency request and bails.
> > > > > > 3. We probably inadvertently catch the DeadlineExceededError, so
> the
> > > > > > runtime doesn't clean up properly.
> > > > > > 4. Future requests are left in a busted state.
> >
> > > > > > Does this sound at all reasonable? I see a few related issues
> (2396,
> > > > > > 2266, and 1409) but no firm/completely clear discussion of what's
> > > > > > happening in any of them.
> >
> > > > > > Thanks,
> > > > > > Dave
> >
> > > > > > PS:
> >
> > > > > > The specifics about our high latency request are *not* strictly
> > > > > > relevant to the larger problem I'm having, but I will include
> them
> > > > > > because I have a second "side" question to ask about it.
> >
> > > > > > The "high latency" request is serving an image. Our app lets
> users
> > > > > > upload images and we store them in the data store. When serving
> an
> > > > > > image, our handler:
> >
> > > > > > 1. Checks to see if the bytes for the image are in memcache, and
> if
> > > so
> > > > > > returns them immediately.
> > > > > > 2. Otherwise grabs the image from the datastore, and if it is
> smaller
> > > > > > than 64K, adds the bytes to the memcache
> > > > > > 3. Returns the result
> >
> > > > > > I'm wondering if using memcache in this

[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." 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

[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." 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]

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

[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,

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]

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.