The last two days the instances kept unstable. Today I kill all
instances hopping this helps. But 3 instances spanned up again and now
every second request to the application fails with the known GAE
problem:

com.google.apphosting.api.DeadlineExceededException: This request
(9706ce3068c95802) started at 2012/08/20 16:05:11.636 UTC and was
still executing at 2012/08/20 16:06:11.214 UTC.
        at 
com.google.appengine.runtime.Request.process-9706ce3068c95802(Request.java)

PLEASE GOOGLE - SOME FEEDBACK / EVALUATIONS WOULD BE NICE !

see also: http://code.google.com/p/googleappengine/issues/detail?id=7910


latest Pingdom History: 
[email protected]       UP alert: krisentalk (www.krisentalk.de) is UP  18:02   
[email protected]       DOWN alert: krisentalk (www.krisentalk.de) is DOWN      
18:01   
[email protected]       UP alert: krisentalk (www.krisentalk.de) is UP  17:59   
[email protected]       DOWN alert: krisentalk (www.krisentalk.de) is DOWN      
17:58   
[email protected]       UP alert: krisentalk (www.krisentalk.de) is UP  17:53   
[email protected]       DOWN alert: krisentalk (www.krisentalk.de) is DOWN      
17:52   
[email protected]       UP alert: krisentalk (www.krisentalk.de) is UP  17:50   
[email protected]       DOWN alert: krisentalk (www.krisentalk.de) is DOWN      
17:47   
[email protected]       UP alert: krisentalk (www.krisentalk.de) is UP  17:45   
[email protected]       DOWN alert: krisentalk (www.krisentalk.de) is DOWN      
17:44   
[email protected]       UP alert: krisentalk (www.krisentalk.de) is UP  17:42   
[email protected]       DOWN alert: krisentalk (www.krisentalk.de) is DOWN      
17:41   
[email protected]       DOWN alert: krisentalk (www.krisentalk.de) is DOWN      
17:35   
[email protected]       UP alert: krisentalk (www.krisentalk.de) is UP  16:52   
[email protected]       DOWN alert: krisentalk (www.krisentalk.de) is DOWN      
16:52   
[email protected]       UP alert: krisentalk (www.krisentalk.de) is UP  04:24   
[email protected]       DOWN alert: krisentalk (www.krisentalk.de) is DOWN      
04:23   
[email protected]       UP alert: krisentalk (www.krisentalk.de) is UP  02:39   
[email protected]       DOWN alert: krisentalk (www.krisentalk.de) is DOWN      
02:38   
[email protected]       UP alert: krisentalk (www.krisentalk.de) is UP  So 
19:16        
[email protected]       DOWN alert: krisentalk (www.krisentalk.de) is DOWN      
So 19:15        
[email protected]       UP alert: krisentalk (www.krisentalk.de) is UP  So 
17:19        
[email protected]       DOWN alert: krisentalk (www.krisentalk.de) is DOWN      
So 17:19        
[email protected]       UP alert: krisentalk (www.krisentalk.de) is UP  So 
16:03        
[email protected]       DOWN alert: krisentalk (www.krisentalk.de) is DOWN      
So 16:02        
[email protected]       UP alert: krisentalk (www.krisentalk.de) is UP  So 5:15 
[email protected]       DOWN alert: krisentalk (www.krisentalk.de) is DOWN      
So 5:14 


On Sat, Aug 18, 2012 at 2:56 PM, Mos <[email protected]> wrote:
> Add again. The last 48 hours the scheduler creates and closes
> instances without reason (traffic as usual, no software updates, no
> special tasks)
>
> That's definitely not a "WorkAsIntended" issue!
>
> As a result instance hours go up and we have to pay again for GAE's
> fault.  Great business-model: Let customers pay for bugs and underline
> it as "WorkAsIntended"!
>
> Check: http://code.google.com/p/googleappengine/issues/detail?id=7910
>
> On Sat, Aug 4, 2012 at 9:00 PM, Mos <[email protected]> wrote:
>> Again a not very reliable GAE month:
>>
>> Pingdom July
>>
>> Uptime   Downtime        Outages         Response time
>> 99.90%  0h 43m 35s      27      466 ms
>>
>>
>> On Wed, Aug 1, 2012 at 11:50 PM, Mos <[email protected]> wrote:
>>> And again I have to pay for GAE issues:
>>>
>>> On Jul 30 the Frontend Instance Hours goes beyond the free limit.
>>> First time this week in my application history. Remember:  The application 
>>> was
>>> unusable on this day because GAE starts instances like crazy (on low 
>>> traffic).
>>> Frontent Instance Hours were consumed of the buggy instance scheduler.
>>>
>>> But to rescue there is another bug in GAE. The billing does not work.
>>> It's stuck for months and I still read the following message on my
>>> billing history:
>>> "We were unable to process your last payment. If the account balance
>>> ($2.32) is not paid in full by 06/01/2012, this application's quotas
>>> may be reset to the free levels."
>>>
>>> That's ingenious, Google.  ;)
>>>
>>>
>>> On Mon, Jul 30, 2012 at 5:47 PM, Mos <[email protected]> wrote:
>>>> Anyone else seeing issue with GAE instance management?
>>>> In one minute - 10 requests - around 5 instances are started. Old ones
>>>> do not response. New instances are created again and again...
>>>>
>>>> http://code.google.com/p/googleappengine/issues/detail?id=7910

-- 
You received this message because you are subscribed to the Google Groups 
"Google App Engine" group.
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