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

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

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

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

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

@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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

up On Oct 4, 10:51 am, sahid sahid.ferdja...@gmail.com wrote: Hello, I have see my warning log and i have a multiple of Request was aborted after waiting too long to attempt to service your request. This may happen sporadically when the App Engine serving cluster is under unexpectedly

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

Hello Sahid, You might want to read/star this issue http://code.google.com/p/googleappengine/issues/detail?id=2396q=waiting%20too%20longcolspec=ID%20Type%20Status%20Priority%20Stars%20Owner%20Summary%20Log%20Component --Stevko On Tue, Oct 5, 2010 at 10:26 AM, sahid sahid.ferdja...@gmail.com

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

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

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

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

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

My cron runs every minute because it is the minimal period that gae supports. 2010/6/16 Tristan tristan.slomin...@gmail.com From my understanding this error happens when a request hits an application instance but is put on a queue and becomes stale before other requests in front of it get

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

How are you keeping the application alive by running a job every minute? Are you queueing tasks to run every second? On Jun 17, 2:17 am, Eduardo Perrino eduardo.perr...@gmail.com wrote: My cron runs every minute because it is the minimal period that gae supports. 2010/6/16 Tristan

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

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

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

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

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

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 michaell...@gmail.com 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

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

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

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

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 joshuaesm...@charter.net wrote: +1  Here is my error: 05-06

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

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

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

See my post on the exact same topic earlier today, too... On May 5, 10:21 am, Mikkel Krautz kra...@gmail.com 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

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

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 b...@pearcomp.com wrote: I'm getting loads of these. It's ok with the deferred tasks, as they

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

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

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

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

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

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) ika...@google.com 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.

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

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) ika...@google.com wrote: Do you see that it's consistent at the same times? What's your application ID? I'll look into

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

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,

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

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

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

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)

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

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 davep...@gmail.com wrote: Ikai, We'll keep

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

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

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

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 markrobertdav...@gmail.com wrote: I am using BlazeDS - a remoting service for Flex. I guess it takes a

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

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) ika...@google.com wrote: What are