This morning 9.00 am brussels time it happens again!! Instances are started but are not healthy. They cannot process any request and they cannot be shut down!!! Beside them are 2 healthy instances which are fro any obscure reason not receiving any request.
I don't know what you are trying to achieve but we would be pleased to know it. Until you get them: Could you implement temporary work around: to serve request only with healthy (instances that do respond to request) and warmed up instances)? PLEASE Le jeudi 14 février 2013 16:44:08 UTC+1, hyperflame a écrit : > > In this mailing list, there has been a lot of discussion on instance > startup times, request queues, etc on the Java runtime (to note a few: > https://groups.google.com/forum/#!msg/google-appengine/sA3o-PTAckc/T2eA64xZ1m0J > https://groups.google.com/forum/#!topic/google-appengine/Y6i9BYQG0Ws ). > > A YCombinator News discussion popped up yesterday discussing many of the > same topics on Heroku, and it's very interesting reading for those > performance tuners out there: *Heroku's Ugly Secret: The story of how the > cloud-king turned its back on Rails > http://news.ycombinator.com/item?id=5215884 * > * > * > The TLDR of the discussion is basically: long request times aren't a GAE/J > only problem, Heroku on Rails is having some of the same difficulties. > > -hyperflame > -- 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?hl=en. For more options, visit https://groups.google.com/groups/opt_out.
