...aaaand started again a few hours ago, i'm guessing due to the 
introduction of 1.9.15.

apologies for harping on this; it just continues to be an interesting 
new(ish) pattern, at least to me.

On Tuesday, October 21, 2014 5:30:11 PM UTC-7, Ryan Barrett wrote:
>
> ...and stopped again, as of 12:30 PST.
>
> On Monday, October 20, 2014 11:28:25 AM UTC-7, Ryan Barrett wrote:
>>
>> just a heads up: this started happening again a few hours ago. my 
>> instances are on 1.9.14 now, and the timing and situation are about the 
>> same, so maybe the same root cause with the new release?
>>
>> On Tuesday, October 7, 2014 4:39:03 PM UTC-7, Ryan Barrett wrote:
>>>
>>> looks like this has stopped as of around 1pm PST today. app engine team, 
>>> if this was a 1.9.13 bug that got fixed, thank you!
>>>
>>> On Monday, October 6, 2014 8:54:04 AM UTC-7, Ryan Barrett wrote:
>>>>
>>>> hi all! starting around 3PM PST yesterday, my instances have started 
>>>> crashing on a small fraction of requests, much more often and consistently 
>>>> than before. (app id s~brid-gy.) the log message is the usual, "A problem 
>>>> was encountered with the process that handled this request, causing it to 
>>>> exit... (Error code 204)"
>>>>
>>>> when this started, i hadn't deployed any new changes since 10/2, and i 
>>>> haven't found anything suspicious and new in my workload or usage pattern. 
>>>> my instances are on 1.9.13, which hasn't been announced yet, so i wonder 
>>>> if 
>>>> the 1.9.13 rollout got to my app yesterday and may have caused this.
>>>>
>>>> has anyone seen a similar bump in instance crashes in their apps since 
>>>> yesterday?
>>>>
>>>

-- 
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 [email protected].
To post to this group, send email to [email protected].
Visit this group at http://groups.google.com/group/google-appengine.
For more options, visit https://groups.google.com/d/optout.

Reply via email to