Deadline exceeded during warm-up

[Bert]

Hi,

Is anyone else experiencing deadline exceeded errors on warm up? Its
been happening for the last hour or so on my app.
My app is running on master-slave datastore. System status says
everything is fine, so perhaps its just me!
On the last instance that just started, the latency was 9 seconds. On
subsequent requests it dropped to 11ms.
Instance...
1 total 0.050 9033.0 ms 28.4 MBytes

Thanks
Rob

[JH]

I used to get these when running Master/Slave, since moving to HRD I
haven't gotten them.

I know that the datastore should not affect startup but some people
have suggested that HRD apps are hosted in another environment. I
don't know if this is true or not but I know I haven't had this issue
since migrating.

[Bert]

Thanks,

Looking to move soon, just haven't taken the step yet.

Thanks
Rob

[todu]

I am seeing a surprising slow response recently and this is with multiple instances showing running in administration dashboard.  

Something has changed in the back-end  hopefully not a permanent thing else my app will become un-usable.

  

[Scott Murphy]

I have been having major problems lately. I am on Master/Slave.  I have Always On and only the middle (2nd) instance always fails out of 3.  It just keeps recycling.  

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

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

[Owen Wiggins]

We've been having similar issues (predominantly during warm up requests) running on Master/Slave for the past several days. This is with always on enabled, if it makes a difference.

AppID: gardenmind-beta

[Karl Rosaen]

Is happening on our app a lot too.  Seeming more and more like the Master/Slave datastore is not a reliable place to be...