Is there any update on this? In addition to instance time increases, we are 
also seeing huge datastore latency past few days and lot 
of DeadlineExceededExceptions. 

Our app id: textyserver

On Wednesday, October 3, 2012 8:27:45 PM UTC-7, Anand Mistry wrote:
>
> Hi Jason,
>
> The engineering team is aware of this issue of instances being in a wacky 
> state, however, I can't give you any more information.
>
> On Thursday, 4 October 2012 06:06:45 UTC+10, Jason Collins wrote:
>>
>> We've seen some Deadline Exceeded Exceptions cropping up on loading 
>> requests again. This used to be commonplace (a couple of years ago), but I 
>> haven't seen it for a long time... until recently.
>>
>> Has anyone else seen this lately? We're seeing it on Py2.7. Normally, 
>> these apps warmup in a couple of seconds, so 60-70s startup times are 
>> completely abnormal.
>>
>> Worse, when this occurs during a loading request, the instance is left in 
>> a "partially inflated" state - in our case, basically all subsequent 
>> requests fail with import/pythonpath issues. Our recourse, once we discover 
>> this is happening, is to manually kill the instance. This really, really 
>> sucks.
>>
>> Can anyone make an argument why you would *want* to keep an instance 
>> that Deadline Exceeded Exceptions on a loading request? I can't. I think an 
>> instance that hits a Deadline Exceeded Exception during a loading request 
>> should be thrown away as suspect.
>>
>> j
>>
>

-- 
You received this message because you are subscribed to the Google Groups 
"Google App Engine" group.
To view this discussion on the web visit 
https://groups.google.com/d/msg/google-appengine/-/joJCKS4A9xEJ.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to 
[email protected].
For more options, visit this group at 
http://groups.google.com/group/google-appengine?hl=en.

Reply via email to