[google-appengine] Scheduler Changes - Disruption

Has anyone else been having major problems since yesterday evening with instances dying after less than 20 requests or 5 minutes where no requests have been served. We have a low traffic app that has been serving consistently well for weeks, several thousand requests to a single instance before

Re: [google-appengine] Scheduler Changes - Disruption

We have the same problem! The other problem is that almost all the loading request are served by front end request and not by the warmup handler. 2014/1/25 Euan Chisholm > Has anyone else been having major problems since yesterday evening with > instances dying after less than 20 requests or 5

[google-appengine] Re: Scheduler Changes - Disruption

For at least one week, I think, after I converted my app from old style to module style. Maybe the change is not related to the conversion. On Saturday, January 25, 2014 6:34:12 PM UTC+8, Euan Chisholm wrote: > > Has anyone else been having major problems since yesterday evening with > instances

[google-appengine] Re: Scheduler Changes - Disruption

The total front end hours per day is changed from about 26 hours to 30 hours. My website's traffic doesn't change much, still about 300 pages and 1000 requests per day. It seems google is very not satisfied with the fact that my app always uses less 28 front end computing hours, so they do some

Re: [google-appengine] High Latency on GoAgent Proxy Server hosted on Google App Engine

General Web Traffic On Fri, Jan 24, 2014 at 11:49 PM, Vinny P wrote: > On Fri, Jan 24, 2014 at 10:00 PM, Nathan Suchy wrote: > > The whole thing is that the application has custom password authentication >> in it and only I can access it. I'm only accessing a web page or two every >> few secon

Re: [google-appengine] Re: Hi, GAE team, I beg you, please don't spawn any dynamic instances for my project, is it possible?

On Saturday, January 25, 2014 10:15:19 AM UTC+8, Rafael Sanches wrote: > > Appenigne had 3 different problems today and even gmail was done > (hopefully unrelated) > > 1) all instances rebooting every 5 minutes > 2) images service api's timing out > 3) high latency to replicate datastore writes

Re: [google-appengine] Confirmed! GAE scheduler is stealing computing hours/money.

I doubt gae scheduler counts the warmup time as billing front computing time now. I remember a googler ever said the warmup time is not counted as billing computing time. Before migrating my app to modules style, gae scheduler counts my app's front end hours as 26.x hours. After the migration,

Re: [google-appengine] High Latency on GoAgent Proxy Server hosted on Google App Engine

*Current Load [image: help] *URI Req/Min currentRequestslast 24 hrsRuntime MCycleslast hrAvg Latencylast hr /2

Re: [google-appengine] High Latency on GoAgent Proxy Server hosted on Google App Engine

That is not a lot of traffic 6.2 requests per minute... On Sat, Jan 25, 2014 at 11:55 AM, Nathan Suchy wrote: > *Current Load [image: help] > * URI Req/Min > current Requestslast 24 hrs Runtime MCycleslast hr Avg Latencylast hr > /

Re: [google-appengine] Confirmed! GAE scheduler is stealing computing hours/money.

On Saturday, January 25, 2014 1:45:47 PM UTC+8, Vinny P wrote: > > On Fri, Jan 24, 2014 at 8:43 PM, Tapir > > wrote: > >> Before converting my app to modules style, the total front instance hours >> were always less than 28 hours. >> > > > > If you still have a copy of your app before you conve

Re: [google-appengine] Confirmed! GAE scheduler is stealing computing hours/money.

My problem is that I don't have too much /_ah/warmup requests so my users waited up to 40/50 seconds to get a response. This is really upsetting me, even because it's not the first time. Il sabato 25 gennaio 2014, Tapir ha scritto: > I doubt gae scheduler counts the warmup time as billing front

[google-appengine] Cache headers modified by Google Frontend

Hi everybody, Do you know why cache headers are modified by Google Frontend servers? Google prohibits my dynamically served static resources to be cached on proxy and user sides. For example, Google set the Expires header to this: Expires: Fri, 01 Jan 1990 00:00:00 GMT And Pragma and Cache-Con

Re: [google-appengine] Confirmed! GAE scheduler is stealing computing hours/money.

you need define a warmup servlet (you must use java, right?) for the url /_ah/warmup, docs: https://developers.google.com/appengine/docs/java/config/appconfig#using_a_custom_warmup_servlet This method is useless for non billing apps, for this method needs a wholly initialized instance running a

Re: [google-appengine] Scheduler Changes - Disruption

We had the exact same issue, where all the instances and modules were rebooting every 5 minutes. We also had an issue that their image service api's were down. That has been fixed, but today we are experiencing HUGE delays when updating an entity. I was used to eventual consistency and 20 seconds

Re: [google-appengine] Re: Lag with google datastore

timh, We're used to eventual consistency and <20 seconds delays between updates in multiple instances. Although, today we are getting more than 10 minutes for the update to replicate. Do you know if the appengine team changed anything yesterday? It's a bit strange that this started happening aft

Re: [google-appengine] Confirmed! GAE scheduler is stealing computing hours/money.

I have defined a servlet, but GAE seems to be very reluctant to use it. Il sabato 25 gennaio 2014, Tapir ha scritto: > you need define a warmup servlet (you must use java, right?) for the url > /_ah/warmup, > docs: > https://developers.google.com/appengine/docs/java/config/appconfig#using_a_cust

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

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

[google-appengine] Front-End instances shutting down

Hi, All my front end instances are shutting down after a few requests or a few seconds after they handle one, causing every new request to spin up a new instance and responding very slow !!! Is anyone experiencing this as well ?? @Google How can we as developers put our apps in gae if things l

[google-appengine] Re: Front-End instances shutting down

Unfortunately in many cases these issues are note widespread - to clarify "doesn't affect all instances". None of my applications have had any errors at all over the last week or so. Whilst a number of people are reporting problems. >From my own personal experience since 2008 , it does seem to