Re: [google-appengine] High Replication latencies and it's related costs.

[Gopal Patel]

if request/second dropped, nothing could be done. latency has nothing to do
with request/second. if nothing else, it will increase the instance count,
google have no control over request/second.

On Wed, Mar 14, 2012 at 9:47 AM, thecheatah  wrote:

> Hi,
>
> I am noticing that the latency on my HR based application went up
> significantly. My app does a simple read and a write. It is taking
> over 1 second to do this operation. In M/S the this operation was <
> 100ms
>
> Even under multi threading, my machines are not processing as many
> requests as my M/S app could handle. My costs have gone up by 50%
> after having switched from M/S. Is this normal?
>
> Last night a single machine handled about 6-7 requests/second. Today
> it has dropped to 4. Nothing has changed. The request are generated by
> devices and thus are very consistent.
>
> It seems that the latency on the HR datastore is causing my cost to
> increase. I have no control over this latency. Is this something I can
> get money back for?
>
> Ravneet
>
> --
> You received this message because you are subscribed to the Google Groups
> "Google App Engine" group.
> To post to this group, send email to google-appengine@googlegroups.com.
> To unsubscribe from this group, send email to
> google-appengine+unsubscr...@googlegroups.com.
> For more options, visit this group at
> http://groups.google.com/group/google-appengine?hl=en.
>
>

-- 
You received this message because you are subscribed to the Google Groups 
"Google App Engine" group.
To post to this group, send email to google-appengine@googlegroups.com.
To unsubscribe from this group, send email to 
google-appengine+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/google-appengine?hl=en.

Re: [google-appengine] Re: It seems "Cold Starts" is an unavoidable problem for GAE. So why not to conquer it?

[Gopal Patel]

you mean, always have one instance more than required ? ( who is going to
pay for that ? ) , and is not minimum idle instance same thing ?

On Wed, Mar 14, 2012 at 10:36 AM, Tapir  wrote:

> I means "why not to conquer it instead of trying to avoid it?".
>
> If you can't conquer it, please lower the instance prices to the
> normal level, I mean about tenth to fifth of the current level so that
> apps can open more resident instances to avoid "Cold Starts".
>
> Here is one solution: give each app one hidden resident instance, when
> an app needs a new instance to handle a coming request, GAE use the
> hidden resident instance to handle the coming request, and open the
> new instance at the same time. Your current "open a new instance and
> let the new coming request to be handled after the new instance is
> warmed up" is not a good implementation.
>
> On Mar 14, 11:51 am, Tapir  wrote:
> > .
>
> --
> You received this message because you are subscribed to the Google Groups
> "Google App Engine" group.
> To post to this group, send email to google-appengine@googlegroups.com.
> To unsubscribe from this group, send email to
> google-appengine+unsubscr...@googlegroups.com.
> For more options, visit this group at
> http://groups.google.com/group/google-appengine?hl=en.
>
>

-- 
You received this message because you are subscribed to the Google Groups 
"Google App Engine" group.
To post to this group, send email to google-appengine@googlegroups.com.
To unsubscribe from this group, send email to 
google-appengine+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/google-appengine?hl=en.

[google-appengine] Re: It seems "Cold Starts" is an unavoidable problem for GAE. So why not to conquer it?

[Tapir]

I means "why not to conquer it instead of trying to avoid it?".

If you can't conquer it, please lower the instance prices to the
normal level, I mean about tenth to fifth of the current level so that
apps can open more resident instances to avoid "Cold Starts".

Here is one solution: give each app one hidden resident instance, when
an app needs a new instance to handle a coming request, GAE use the
hidden resident instance to handle the coming request, and open the
new instance at the same time. Your current "open a new instance and
let the new coming request to be handled after the new instance is
warmed up" is not a good implementation.

On Mar 14, 11:51 am, Tapir  wrote:
> .

-- 
You received this message because you are subscribed to the Google Groups 
"Google App Engine" group.
To post to this group, send email to google-appengine@googlegroups.com.
To unsubscribe from this group, send email to 
google-appengine+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/google-appengine?hl=en.

[google-appengine] High Replication latencies and it's related costs.

[thecheatah]

Hi,

I am noticing that the latency on my HR based application went up
significantly. My app does a simple read and a write. It is taking
over 1 second to do this operation. In M/S the this operation was <
100ms

Even under multi threading, my machines are not processing as many
requests as my M/S app could handle. My costs have gone up by 50%
after having switched from M/S. Is this normal?

Last night a single machine handled about 6-7 requests/second. Today
it has dropped to 4. Nothing has changed. The request are generated by
devices and thus are very consistent.

It seems that the latency on the HR datastore is causing my cost to
increase. I have no control over this latency. Is this something I can
get money back for?

Ravneet

-- 
You received this message because you are subscribed to the Google Groups 
"Google App Engine" group.
To post to this group, send email to google-appengine@googlegroups.com.
To unsubscribe from this group, send email to 
google-appengine+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/google-appengine?hl=en.

[google-appengine] 3 months passed, hi, googlers, when will the unvisited groups be removed from the profile pages?

[Tapir]

http://groups.google.com/group/google-appengine/browse_thread/thread/fb06574b6ed8b726/8ff0423956353fe3?lnk=gst&q=wtf#8ff0423956353fe3

Hi Gregory and Ikai, do you care about it?
http://groups.google.com/groups/profile?enc_user=Zv7tuxCy4JMQo8Z2z60KpjGFZb6i
http://groups.google.com/groups/profile?enc_user=GuejVxEAAABpq3LE9LlvXst-Z8GVcBllkdEasx1kiYTQavV7mdW13Q

-- 
You received this message because you are subscribed to the Google Groups 
"Google App Engine" group.
To post to this group, send email to google-appengine@googlegroups.com.
To unsubscribe from this group, send email to 
google-appengine+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/google-appengine?hl=en.

[google-appengine] It seems "Cold Starts" is an unavoidable problem for GAE. So why not to conquer it?

[Tapir]

.

-- 
You received this message because you are subscribed to the Google Groups 
"Google App Engine" group.
To post to this group, send email to google-appengine@googlegroups.com.
To unsubscribe from this group, send email to 
google-appengine+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/google-appengine?hl=en.

[google-appengine] Re: Problem with mail quota

[Daniel]

I'm seeing the same problem! I have hit 100 emails and can't mail anymore 
even with a very generous billing quota per day.. billable email is not 
triggering.  

My app is sky-words-hrd



On Wednesday, February 8, 2012 2:36:40 PM UTC-8, Ice13ill wrote:
>
> In SDK 1.6.2 is stated that: 
>  "Mail Quota for App Engine apps that have signed up for billing 
> will only be increased after the first payment for the app is 
> processed. " 
>
> In the documentation I found this: 
> "100 recipients until first charge cleared; 2000 recipients free and 
> no maximum thereafter" 
>
> The problem is that my app has billing enabled for a very long time 
> and although everything was ok until today (i also checked the billing 
> history and emails that exceeded the 100 limit were billed 
> correctly) , now my app has reached 100 mail quota and it cannot send 
> any more emails... 
>
> Does anyone else has this problem ?

-- 
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/-/AYlR59U_ChkJ.
To post to this group, send email to google-appengine@googlegroups.com.
To unsubscribe from this group, send email to 
google-appengine+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/google-appengine?hl=en.

Re: [google-appengine] Re: Outages?

[Mauricio Aristizabal]

Potential fix: set performance sliders to auto.

This is purely anecdotal but it might mean something:  After reading some
post this afternoon about the instance settings not really working I
switched to AUTO idle instances and AUTO pending latency (before they were
set to 1-1 and 25ms-1.5s respectively).

That was about 5 hours ago, and within an hour or so everything started
working fine.  Before that, problems had been continuous as far as I could
tell for 6 days or so.

Or maybe the AppEngine guys finally got it under control.



On Tue, Mar 13, 2012 at 5:58 PM, stephenp  wrote:

> One more here.
>
> appid: carglyplatform (HRD)
>
> It's been flaky off-and-on for a couple weeks, yesterday was better, today
> bad again. Lots of warmup errors, instance restarts, errors in general.
>
> Stephen
>
>
> On Tuesday, March 6, 2012 3:17:37 PM UTC-6, Adam Sherman wrote:
>
>> Am I the only one seeing short duration outages? They are being reflected
>> at:
>>
>> http://code.google.com/status/**appengine
>>
>> But I don't see anyone else complaining anywhere, so it makes me worried.
>>
>> A.
>>
>>
> On Tuesday, March 6, 2012 3:17:37 PM UTC-6, Adam Sherman wrote:
>
>> Am I the only one seeing short duration outages? They are being reflected
>> at:
>>
>> http://code.google.com/status/**appengine
>>
>> But I don't see anyone else complaining anywhere, so it makes me worried.
>>
>> A.
>>
>>
> On Tuesday, March 6, 2012 3:17:37 PM UTC-6, Adam Sherman wrote:
>
>> Am I the only one seeing short duration outages? They are being reflected
>> at:
>>
>> http://code.google.com/status/**appengine
>>
>> But I don't see anyone else complaining anywhere, so it makes me worried.
>>
>> A.
>>
>>  --
> 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/-/C5nrBOmPaPcJ.
>
> To post to this group, send email to google-appengine@googlegroups.com.
> To unsubscribe from this group, send email to
> google-appengine+unsubscr...@googlegroups.com.
> For more options, visit this group at
> http://groups.google.com/group/google-appengine?hl=en.
>

-- 
You received this message because you are subscribed to the Google Groups 
"Google App Engine" group.
To post to this group, send email to google-appengine@googlegroups.com.
To unsubscribe from this group, send email to 
google-appengine+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/google-appengine?hl=en.

[google-appengine] Re: Outages?

[stephenp]

One more here.

appid: carglyplatform (HRD)

It's been flaky off-and-on for a couple weeks, yesterday was better, today 
bad again. Lots of warmup errors, instance restarts, errors in general.

Stephen

On Tuesday, March 6, 2012 3:17:37 PM UTC-6, Adam Sherman wrote:
>
> Am I the only one seeing short duration outages? They are being reflected 
> at:
>
> http://code.google.com/status/appengine
>
> But I don't see anyone else complaining anywhere, so it makes me worried.
>
> A.
>
>
On Tuesday, March 6, 2012 3:17:37 PM UTC-6, Adam Sherman wrote:
>
> Am I the only one seeing short duration outages? They are being reflected 
> at:
>
> http://code.google.com/status/appengine
>
> But I don't see anyone else complaining anywhere, so it makes me worried.
>
> A.
>
>
On Tuesday, March 6, 2012 3:17:37 PM UTC-6, Adam Sherman wrote:
>
> Am I the only one seeing short duration outages? They are being reflected 
> at:
>
> http://code.google.com/status/appengine
>
> But I don't see anyone else complaining anywhere, so it makes me worried.
>
> A.
>
>

-- 
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/-/C5nrBOmPaPcJ.
To post to this group, send email to google-appengine@googlegroups.com.
To unsubscribe from this group, send email to 
google-appengine+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/google-appengine?hl=en.

Re: [google-appengine] Re: Lots of HTTP 500 errors and all instances restarted by GAE!

[Mos]

Vote for the issue:
http://code.google.com/p/googleappengine/issues/detail?id=7133

I hope Google will give some feedback soon ?!

On Tue, Mar 13, 2012 at 5:41 PM, Nicanor Babula wrote:

> Same thing here too!
>
> appid: domodentweb2
> datastore: HRD
>
> Getting calls and emails from angry customers.
> Please, help!
> Thanks.
>
> On Tue, Mar 13, 2012 at 5:38 PM, Mark  wrote:
>
>> This is happening to me too.  Instances getting restarted, and requests
>> taking way longer than usual.  Getting emails from unhappy users.
>>
>> My app id is bedbuzzserver, on HR ( & Java)
>>
>> --
>> 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/-/gX9u1do57t0J.
>>
>> To post to this group, send email to google-appengine@googlegroups.com.
>> To unsubscribe from this group, send email to
>> google-appengine+unsubscr...@googlegroups.com.
>> For more options, visit this group at
>> http://groups.google.com/group/google-appengine?hl=en.
>>
>
>
>
> --
> Nicanor Cristian Babula
>
>  --
> You received this message because you are subscribed to the Google Groups
> "Google App Engine" group.
> To post to this group, send email to google-appengine@googlegroups.com.
> To unsubscribe from this group, send email to
> google-appengine+unsubscr...@googlegroups.com.
> For more options, visit this group at
> http://groups.google.com/group/google-appengine?hl=en.
>

-- 
You received this message because you are subscribed to the Google Groups 
"Google App Engine" group.
To post to this group, send email to google-appengine@googlegroups.com.
To unsubscribe from this group, send email to 
google-appengine+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/google-appengine?hl=en.

Re: [google-appengine] Re: Lots of HTTP 500 errors and all instances restarted by GAE!

[Nicanor Babula]

Same thing here too!

appid: domodentweb2
datastore: HRD

Getting calls and emails from angry customers.
Please, help!
Thanks.

On Tue, Mar 13, 2012 at 5:38 PM, Mark  wrote:

> This is happening to me too.  Instances getting restarted, and requests
> taking way longer than usual.  Getting emails from unhappy users.
>
> My app id is bedbuzzserver, on HR ( & Java)
>
> --
> 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/-/gX9u1do57t0J.
>
> To post to this group, send email to google-appengine@googlegroups.com.
> To unsubscribe from this group, send email to
> google-appengine+unsubscr...@googlegroups.com.
> For more options, visit this group at
> http://groups.google.com/group/google-appengine?hl=en.
>



-- 
Nicanor Cristian Babula

-- 
You received this message because you are subscribed to the Google Groups 
"Google App Engine" group.
To post to this group, send email to google-appengine@googlegroups.com.
To unsubscribe from this group, send email to 
google-appengine+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/google-appengine?hl=en.

Re: [google-appengine] Re: 1:1 with a member of the App Engine community: Robert Kluin

[Robert Kluin]

Hey Guys, glad you found it "entertaining" (not sure the right word).
Just wanted to note that I'm at pycon this evening hacking around on a
couple things.  For anyone here, feel free to drop by!  I'll be taking
off tomorrow mid-morning.


Robert






On Tue, Mar 13, 2012 at 14:24, Kaan Soral  wrote:
> I'm a big fan of robertk, loved the interview
>
>
> On Tuesday, March 13, 2012 12:13:25 AM UTC+2, Johan Euphrosine (Google)
> wrote:
>>
>> FYI,
>>
>> I just posted an interview with our very Robert Kluin to Google+:
>> https://plus.google.com/111042085517496880918/posts/8CHm8KKqXWU
>>
>> Feel free to comment there.
>> --
>> Johan Euphrosine (proppy)
>> Developer Programs Engineer
>> Google Developer Relations
>
> --
> 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/-/BjsPhqc6ZNsJ.
>
> To post to this group, send email to google-appengine@googlegroups.com.
> To unsubscribe from this group, send email to
> google-appengine+unsubscr...@googlegroups.com.
> For more options, visit this group at
> http://groups.google.com/group/google-appengine?hl=en.

-- 
You received this message because you are subscribed to the Google Groups 
"Google App Engine" group.
To post to this group, send email to google-appengine@googlegroups.com.
To unsubscribe from this group, send email to 
google-appengine+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/google-appengine?hl=en.

[google-appengine] Re: Eclipse + GAE, Problem in project clean

[Carlos]

I have found the solution to my problem. It seems to be the length of the 
arguments passed to the enhacer... follow this link: 
http://stackoverflow.com/questions/1890410/base-class-does-not-seem-to-have-been-enhanced-after-upgrade-of-google-app-eng

Carlos

-- 
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/-/XIof0SXbVrEJ.
To post to this group, send email to google-appengine@googlegroups.com.
To unsubscribe from this group, send email to 
google-appengine+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/google-appengine?hl=en.

[google-appengine] Re: Outages?

[Nicanor Babula]

We are having the same problems.

appid: domodentweb2
QPS: 0.28
%error: can't say... It's fluctuating. In15 minutes periods we can have 0%, 
or 80+%
datastore: HRD

Please help. 
Thanks. 

Il giorno martedì 6 marzo 2012 22:17:37 UTC+1, Adam Sherman ha scritto:
>
> Am I the only one seeing short duration outages? They are being reflected 
> at:
>
> http://code.google.com/status/appengine
>
> But I don't see anyone else complaining anywhere, so it makes me worried.
>
> A.
>
>

-- 
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/-/sXYBEWtTK3MJ.
To post to this group, send email to google-appengine@googlegroups.com.
To unsubscribe from this group, send email to 
google-appengine+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/google-appengine?hl=en.

[google-appengine] Channel API is working locally But not in production throws provided token is invalid

[praveen kumar]

 I will create channel Id(token)  using Channel API in server side.,
In the client side using this token while opening the channel using
http://talkgadget.google.com/talkgadget/channel.js. It throwing error
provider token is invalid .

Please help how to fix this issue

Regards.,
Praveen.

-- 
You received this message because you are subscribed to the Google Groups 
"Google App Engine" group.
To post to this group, send email to google-appengine@googlegroups.com.
To unsubscribe from this group, send email to 
google-appengine+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/google-appengine?hl=en.

[google-appengine] Channel API is working locally But not in production throws provided token is invalid

[praveen]

  I will create channel Id(token)  using Channel API in server side.,
In the client side using this token while opening the channel using
http://talkgadget.google.com/talkgadget/channel.js. It throwing error
provider token is invalid .

Please help how to fix this issue

-- 
You received this message because you are subscribed to the Google Groups 
"Google App Engine" group.
To post to this group, send email to google-appengine@googlegroups.com.
To unsubscribe from this group, send email to 
google-appengine+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/google-appengine?hl=en.

[google-appengine] Re: Outages?

[Nicanor Babula]

Hi, 

We are having the same issues.
appid: domodentweb2
QPS: 0.028
%error: I would say 60%, but it's not accurate
Datastore: HRD.

We are desperate because there is no backup alternative, so if appengine is 
down, we are down..

Thanks.

Il giorno martedì 6 marzo 2012 22:17:37 UTC+1, Adam Sherman ha scritto:
>
> Am I the only one seeing short duration outages? They are being reflected 
> at:
>
> http://code.google.com/status/appengine
>
> But I don't see anyone else complaining anywhere, so it makes me worried.
>
> A.
>
>

-- 
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/-/d66IpCutaAsJ.
To post to this group, send email to google-appengine@googlegroups.com.
To unsubscribe from this group, send email to 
google-appengine+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/google-appengine?hl=en.

[google-appengine] Re: Outages?

[Matt Cameron]

We are seeing lots of 500s today.  Nothing shown on the appengine status 
board.

On Tuesday, 6 March 2012 13:17:37 UTC-8, Adam Sherman wrote:
>
> Am I the only one seeing short duration outages? They are being reflected 
> at:
>
> http://code.google.com/status/appengine
>
> But I don't see anyone else complaining anywhere, so it makes me worried.
>
> A.
>
>

-- 
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/-/3PfTuYGfni0J.
To post to this group, send email to google-appengine@googlegroups.com.
To unsubscribe from this group, send email to 
google-appengine+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/google-appengine?hl=en.

[google-appengine] Re: Outages?

[Chris Merrill]

Our app is running on HRD and performance has, on average, been fine over 
the past 2 weeks. But this morning, our app is unusable. Almost every 
request times out. Note that our app was last deployed 2 weeks ago - no 
changes since then. Our staging application has newer code but a LOT less 
data in it - it shows the same symptoms. Even our login page times out most 
of the time!

AppEngine status panel say everything is ok, but we're dead in the water  :(


On Tuesday, March 6, 2012 4:17:37 PM UTC-5, Adam Sherman wrote:
>
> Am I the only one seeing short duration outages? They are being reflected 
> at:
>
> http://code.google.com/status/appengine
>
> But I don't see anyone else complaining anywhere, so it makes me worried.
>
> A.
>
>

-- 
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/-/FNdbMiVfAGEJ.
To post to this group, send email to google-appengine@googlegroups.com.
To unsubscribe from this group, send email to 
google-appengine+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/google-appengine?hl=en.

Re: [google-appengine] Re: 500 errors + high latency + please communicate with us

[Rui Oliveira]

>
> Hi Ikai,
>

My appId is phone-menu. 

I'm with the same problem.


My conclusions:

After deploy in the next 10 minutes I get a lot of errors. After that the 
default version will run ok( not completely ok).
Concurrent request on the first 10 seconds will improve the probability to 
get errors
Default version works much better than the other versions. The probability 
to get an error from no default versions is very high. ( 

 an unexpected exception: 
com.google.apphosting.api.ApiProxy$CancelledException: The API call 
datastore_v3.RunQuery() was explicitly cancelled.

at 
com.google.gwt.user.server.rpc.RPC.encodeResponseForFailure(RPC.java:385)
at 
com.google.gwt.user.server.rpc.RPC.invokeAndEncodeResponse(RPC.java:588)
at 
com.google.gwt.user.server.rpc.RemoteServiceServlet.processCall(RemoteServiceServlet.java:208)
at 
com.google.gwt.user.server.rpc.RemoteServiceServlet.processPost(RemoteServiceServlet.java:248)
at 
com.google.gwt.user.server.rpc.AbstractRemoteServiceServlet.doPost(AbstractRemoteServiceServlet.java:62)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:637)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:717)
at 
org.mortbay.jetty.servlet.ServletHolder.handle(ServletHolder.java:511)
at 
org.mortbay.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1166)
at 
com.google.apphosting.utils.servlet.ParseBlobUploadFilter.doFilter(ParseBlobUploadFilter.java:102)
at 
org.mortbay.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1157)
at 
com.google.apphosting.runtime.jetty.SaveSessionFilter.doFilter(SaveSessionFilter.java:35)
at 
org.mortbay.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1157)
at 
com.google.apphosting.utils.servlet.TransactionCleanupFilter.doFilter(TransactionCleanupFilter.java:43)
at 
org.mortbay.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1157)
at 
org.mortbay.jetty.servlet.ServletHandler.handle(ServletHandler.java:388)
at 
org.mortbay.jetty.security.SecurityHandler.handle(SecurityHandler.java:216)
at 
org.mortbay.jetty.servlet.SessionHandler.handle(SessionHandler.java:182)
at 
org.mortbay.jetty.handler.ContextHandler.handle(ContextHandler.java:765)
at org.mortbay.jetty.webapp.WebAppContext.handle(WebAppContext.java:418)
at 
com.google.apphosting.runtime.jetty.AppVersionHandlerMap.handle(AppVersionHandlerMap.java:249)
at 
org.mortbay.jetty.handler.HandlerWrapper.handle(HandlerWrapper.java:152)
at org.mortbay.jetty.Server.handle(Server.java:326)
at 
org.mortbay.jetty.HttpConnection.handleRequest(HttpConnection.java:542)
at 
org.mortbay.jetty.HttpConnection$RequestHandler.headerComplete(HttpConnection.java:923)
at 
com.google.apphosting.runtime.jetty.RpcRequestParser.parseAvailable(RpcRequestParser.java:76)
at org.mortbay.jetty.HttpConnection.handle(HttpConnection.java:404)
at 
com.google.apphosting.runtime.jetty.JettyServletEngineAdapter.serviceRequest(JettyServletEngineAdapter.java:135)
at 
com.google.apphosting.runtime.JavaRuntime$RequestRunnable.run(JavaRuntime.java:422)
at 
com.google.tracing.TraceContext$TraceContextRunnable.runInContext(TraceContext.java:449)
at 
com.google.tracing.TraceContext$TraceContextRunnable$1.run(TraceContext.java:455)
at com.google.tracing.TraceContext.runInContext(TraceContext.java:695)
at 
com.google.tracing.TraceContext$AbstractTraceContextCallback.runInInheritedContextNoUnref(TraceContext.java:333)
at 
com.google.tracing.TraceContext$AbstractTraceContextCallback.runInInheritedContext(TraceContext.java:325)
at 
com.google.tracing.TraceContext$TraceContextRunnable.run(TraceContext.java:453)
at 
com.google.apphosting.runtime.ThreadGroupPool$PoolEntry.run(ThreadGroupPool.java:251)
at java.lang.Thread.run(Thread.java:679)
Caused by: com.google.apphosting.api.ApiProxy$CancelledException: The API call 
datastore_v3.RunQuery() was explicitly cancelled.

-- 
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/-/Z2iQ_7Twsn8J.
To post to this group, send email to google-appengine@googlegroups.com.
To unsubscribe from this group, send email to 
google-appengine+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/google-appengine?hl=en.

[google-appengine] Re: Datastore offline as of 3:40pm PST

[devlike]

3 days later, the service status page shows all green for the past week.  
Seems a bit less than honest.

-- 
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/-/pWUz1T_OFAUJ.
To post to this group, send email to google-appengine@googlegroups.com.
To unsubscribe from this group, send email to 
google-appengine+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/google-appengine?hl=en.

Re: [google-appengine] Re: Outages?

[j]

Ikai,

I have not moved to HRD yet. But I am pretty sure I am the only user of my 
application. However, ever since couples of days back, not only that it is 
slow but I kept on running out of quota, despite the fact that I turned on 
the billing. I have switched off billing yesterday as it didn't help me.

Can I get a refund? The request is due to the fact that I am hitting the 
app less than 20 times per day, and I run out of quotas. Enabled billing 
didn't help. I am perplexed with a single user, how would it be possible to 
exhaust 0.05 million operations? see below as an example -

Datastore Read Operations
[image: 100%]
100%0.05 of 0.05 Million Ops0.00$0.70/ Million Ops$0.00

I don't want publish my appid, if you would like to know, I get text you at 
your google voice number. If that helps.

Thanks for any reply.

On Monday, March 12, 2012 2:52:29 PM UTC-4, Ikai Lan wrote:
>
> Hi Riley,
>
> That's a legitimate question, and one that we haven't officially answered 
> yet. It's certainly the direction that things have been moving simply due 
> to the nature of production management. Given that the SLA applies to HRD 
> and not master/slave applications, you are definitely going to get a better 
> quality of service migrating to HRD. In fact, I strongly advise that you do 
> so. 
>
> One challenge that we have when dealing with issues is to decide whether 
> we should do emergency maintenance that requires downtime. With any 
> production system, it's not always guaranteed that maintenance will result 
> in issues being completely resolved, which would be really bad for app 
> developers. At what threshold do we determine that a downtime with no 
> guarantee of addressing the issues is worthwhile? Global 0.1% error rate? 
> 1%? The call is not always clear cut because those errors may not be evenly 
> distributed, and the impact may be huge, or it may be small. With 
> master/slave applications, we do what we can to address the short term 
> symptoms as well as the underlying system issues without impacting serving, 
> which is often an order of magnitude more difficult (It kind of reminds me 
> of that scene in Indiana Jones where he takes an artifact, swapping it with 
> a bag of sand as quickly as possible to try to avoid setting off traps. 
> Pillaging of historic artifacts is way easier when it's not dangerous, not 
> speaking from personal experience). When your application runs on High 
> Replication, the call is easy: there's no downtime required in 99% of 
> cases, so we perform the maintenance right away because if it doesn't 
> address the issue, there's no serving downtime for users.
>
> If you're not subscribed to downtime-notify, I recommend that you do so. 
> Announcements like this will NOT and never will be moving to StackOverflow:
>
>
> https://groups.google.com/forum/?fromgroups#!forum/google-appengine-downtime-notify
>
> We may be announcing a maintenance in the very near future that will 
> impact the serving of master/slave applications.
>
> --
> Ikai Lan 
> Developer Programs Engineer, Google App Engine
> plus.ikailan.com
>
>
>
> On Mon, Mar 12, 2012 at 9:46 AM, Riley  wrote:
>
>> Ikai, it sounds like support for HR apps is being prioritized.  Is that 
>> the case? Should we expect that to be the case in the future? Sorry if 
>> that's documented somewhere already~
>>
>> Riley
>>
>>
>> On Monday, March 12, 2012 11:44:59 AM UTC-5, Riley wrote:
>>>
>>> Our appid is activegrade, we use the m/s datastore, and get from 0-10 
>>> QPS throughout the day.  Normally we have 1-4 instances running, but since 
>>> this seems *mostly* related to startup, we dedicated 10 idle resident 
>>> instances to run all the time.  This covers us a little, but still, when a 
>>> user triggers a new instance, they get the 60+ second wait and then an 
>>> error. Ugh!  Our costs are relatively minor - about $20 a day now that we 
>>> are running these 10 ordinarily unnecessary instances - but this is a big 
>>> cost for us, and embarrassing too.
>>>
>>> On Tuesday, March 6, 2012 3:17:37 PM UTC-6, Adam Sherman wrote:

 Am I the only one seeing short duration outages? They are being 
 reflected at:

 http://code.google.com/status/**appengine

 But I don't see anyone else complaining anywhere, so it makes me 
 worried.

 A.

  -- 
>> 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/-/VzKRK5UG96MJ.
>>
>> To post to this group, send email to google-appengine@googlegroups.com.
>> To unsubscribe from this group, send email to 
>> google-appengine+unsubscr...@googlegroups.com.
>> For more options, visit this group at 
>> http://groups.google.com/group/google-appengine?hl=en.
>>
>
>

-- 
You received this message because you are subscribed to the Google Groups 
"Google App Engin

[google-appengine] Java Error code 104: A problem was encountered with the process that handled this request, causing it to exit

[Matt Mastracci]

Hey all,

Has anyone been seeing a large number of error code 104s today? We haven't 
made any significant code changes today, but these started showing up in 
logs, with no additional information.

I've tried upgrading our instance types to F2, just in case we're hitting 
some sort of memory limit, but it doesn't appear to have helped. I've 
noticed that there's a Java issue on the status screen: could this be 
related?

Attached is a graph showing the milliseconds/request graph, which seems to 
correlate with the issue we've been seeing.


   1. 
  1. 
  
  A problem was encountered with the process that handled this request, 
causing it to exit. This is likely to cause a new process to be used for the 
next request to your application. If you see this message frequently, you may 
be throwing exceptions during the initialization of your application. (Error 
code 104)
  
  2. 
  1. 
   

-- 
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/-/T12g_EHTjigJ.
To post to this group, send email to google-appengine@googlegroups.com.
To unsubscribe from this group, send email to 
google-appengine+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/google-appengine?hl=en.

<>

[google-appengine] using GAE with javascript

[that an]

I'm looking for a way to use javascript code to directly interface
with the google app engine and with the datastore.

I've already used the GWT/GAE Java SDK in Eclipse with varying levels
of success, but I'm looking for a way to leverage the benefits of GAE
cloud services with the direct DOM manipulation of writing javascript
directly for the client.  GWT front end just doesn't seem flexible
enough to do what javascript can.

Maybe I've missed something obvious, or something that is out there
does it, but I've been searching for awhile now, and it just seems
like Google is dancing around any direct client access to their App
Engine and cloud datastore.

I've pretty much exhausted my leads so far - Any direction is greatly
appreciated.

-- 
You received this message because you are subscribed to the Google Groups 
"Google App Engine" group.
To post to this group, send email to google-appengine@googlegroups.com.
To unsubscribe from this group, send email to 
google-appengine+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/google-appengine?hl=en.

[google-appengine] Re: Api.Files.Finalize fails permanently

[Moises Belchin]

More info about that here:

https://developers.google.com/storage/docs/accesscontrol

Regards.

2012/3/13 Moises Belchin 

> My problem was solved !!!
>
> When I create the file I set ACL to 'public-read' and It worked !!
>
> However if you used ACL = 'public-read-write' It fails, because
> public-read-write applies only for buckets, be careful with that !
>
> Regards and I hope this will be useful for you.
>
> Thanks all !
>
> 2012/3/13 Moises Belchin 
>
>> Hi all,
>>
>> I do a very simple test. Create gs file, write info to it and
>> finalize.
>> My App Engine app have permission to Google Cloud Storage as OWNER
>>
>> I test that from my AppEngine app and I test from remote api.
>>
>> ## CODE ##
>>
>> path = /gs/bucket/MyFile
>> mime_type = 'application/octet-stream'
>> acl = 'public-read-write'
>> write_path = files.gs.create(path, mime_type = mime_type, acl = acl)
>>
>> q = MyModel.query()
>> regs = q.fetch()
>> for r in regs:
>>  with files.open(write_path, 'a') as fp:
>>fp.write(str(r))
>>
>> # When I do finalize or f.close(finalized = True) Always fails and
>> give me ERROR 1
>> files.finalize(write_path)
>>
>> ## END CODE ##
>>
>> ## ERROR 1 ##
>> Traceback (most recent call last):
>>  File "/base/python27_runtime/python27_lib/versions/1/google/
>> appengine/ext/admin/__init__.py", line 317, in post
>>exec(compiled_code, globals())
>>  File "", line 43, in 
>>  File "/base/data/home/apps/s~semtable/v51r05.357456670132838042/
>> utils.py", line 1080, in finalize
>>files.finalize(write_path)
>>  File "/base/python27_runtime/python27_lib/versions/1/google/
>> appengine/api/files/file.py", line 450, in finalize
>>f.close(finalize=True)
>>  File "/base/python27_runtime/python27_lib/versions/1/google/
>> appengine/api/files/file.py", line 277, in close
>>self._make_rpc_call_with_retry('Close', request, response)
>>  File "/base/python27_runtime/python27_lib/versions/1/google/
>> appengine/api/files/file.py", line 390, in _make_rpc_call_with_retry
>>_make_call(method, request, response)
>>  File "/base/python27_runtime/python27_lib/versions/1/google/
>> appengine/api/files/file.py", line 238, in _make_call
>>_raise_app_error(e)
>>  File "/base/python27_runtime/python27_lib/versions/1/google/
>> appengine/api/files/file.py", line 172, in _raise_app_error
>>raise UnknownError()
>> UnknownError
>> ## END ERROR 1 ##
>>
>> How can I resolve this problem?
>>
>> Thanks so much.
>>
>
>
>
> --
> Saludos.
> Moisés Belchín.
>
>


-- 
Saludos.
Moisés Belchín.

-- 
You received this message because you are subscribed to the Google Groups 
"Google App Engine" group.
To post to this group, send email to google-appengine@googlegroups.com.
To unsubscribe from this group, send email to 
google-appengine+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/google-appengine?hl=en.

[google-appengine] Re: Api.Files.Finalize fails permanently

[Moises Belchin]

My problem was solved !!!

When I create the file I set ACL to 'public-read' and It worked !!

However if you used ACL = 'public-read-write' It fails, because
public-read-write applies only for buckets, be careful with that !

Regards and I hope this will be useful for you.

Thanks all !

2012/3/13 Moises Belchin 

> Hi all,
>
> I do a very simple test. Create gs file, write info to it and
> finalize.
> My App Engine app have permission to Google Cloud Storage as OWNER
>
> I test that from my AppEngine app and I test from remote api.
>
> ## CODE ##
>
> path = /gs/bucket/MyFile
> mime_type = 'application/octet-stream'
> acl = 'public-read-write'
> write_path = files.gs.create(path, mime_type = mime_type, acl = acl)
>
> q = MyModel.query()
> regs = q.fetch()
> for r in regs:
>  with files.open(write_path, 'a') as fp:
>fp.write(str(r))
>
> # When I do finalize or f.close(finalized = True) Always fails and
> give me ERROR 1
> files.finalize(write_path)
>
> ## END CODE ##
>
> ## ERROR 1 ##
> Traceback (most recent call last):
>  File "/base/python27_runtime/python27_lib/versions/1/google/
> appengine/ext/admin/__init__.py", line 317, in post
>exec(compiled_code, globals())
>  File "", line 43, in 
>  File "/base/data/home/apps/s~semtable/v51r05.357456670132838042/
> utils.py", line 1080, in finalize
>files.finalize(write_path)
>  File "/base/python27_runtime/python27_lib/versions/1/google/
> appengine/api/files/file.py", line 450, in finalize
>f.close(finalize=True)
>  File "/base/python27_runtime/python27_lib/versions/1/google/
> appengine/api/files/file.py", line 277, in close
>self._make_rpc_call_with_retry('Close', request, response)
>  File "/base/python27_runtime/python27_lib/versions/1/google/
> appengine/api/files/file.py", line 390, in _make_rpc_call_with_retry
>_make_call(method, request, response)
>  File "/base/python27_runtime/python27_lib/versions/1/google/
> appengine/api/files/file.py", line 238, in _make_call
>_raise_app_error(e)
>  File "/base/python27_runtime/python27_lib/versions/1/google/
> appengine/api/files/file.py", line 172, in _raise_app_error
>raise UnknownError()
> UnknownError
> ## END ERROR 1 ##
>
> How can I resolve this problem?
>
> Thanks so much.
>



-- 
Saludos.
Moisés Belchín.

-- 
You received this message because you are subscribed to the Google Groups 
"Google App Engine" group.
To post to this group, send email to google-appengine@googlegroups.com.
To unsubscribe from this group, send email to 
google-appengine+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/google-appengine?hl=en.

[google-appengine] Api.Files.Finalize fails permanently

[Moises Belchin]

Hi all,

I do a very simple test. Create gs file, write info to it and
finalize.
My App Engine app have permission to Google Cloud Storage as OWNER

I test that from my AppEngine app and I test from remote api.

## CODE ##

path = /gs/bucket/MyFile
mime_type = 'application/octet-stream'
acl = 'public-read-write'
write_path = files.gs.create(path, mime_type = mime_type, acl = acl)

q = MyModel.query()
regs = q.fetch()
for r in regs:
  with files.open(write_path, 'a') as fp:
fp.write(str(r))

# When I do finalize or f.close(finalized = True) Always fails and
give me ERROR 1
files.finalize(write_path)

## END CODE ##

## ERROR 1 ##
Traceback (most recent call last):
  File "/base/python27_runtime/python27_lib/versions/1/google/
appengine/ext/admin/__init__.py", line 317, in post
exec(compiled_code, globals())
  File "", line 43, in 
  File "/base/data/home/apps/s~semtable/v51r05.357456670132838042/
utils.py", line 1080, in finalize
files.finalize(write_path)
  File "/base/python27_runtime/python27_lib/versions/1/google/
appengine/api/files/file.py", line 450, in finalize
f.close(finalize=True)
  File "/base/python27_runtime/python27_lib/versions/1/google/
appengine/api/files/file.py", line 277, in close
self._make_rpc_call_with_retry('Close', request, response)
  File "/base/python27_runtime/python27_lib/versions/1/google/
appengine/api/files/file.py", line 390, in _make_rpc_call_with_retry
_make_call(method, request, response)
  File "/base/python27_runtime/python27_lib/versions/1/google/
appengine/api/files/file.py", line 238, in _make_call
_raise_app_error(e)
  File "/base/python27_runtime/python27_lib/versions/1/google/
appengine/api/files/file.py", line 172, in _raise_app_error
raise UnknownError()
UnknownError
## END ERROR 1 ##

How can I resolve this problem?

Thanks so much.

-- 
You received this message because you are subscribed to the Google Groups 
"Google App Engine" group.
To post to this group, send email to google-appengine@googlegroups.com.
To unsubscribe from this group, send email to 
google-appengine+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/google-appengine?hl=en.

[google-appengine] Re: Outages?

[Vincent]

Hi GAE guys,

same issue for us ... please react ... our cutomers are complaining :-(

appid: logos-contacts 

Regards 
Vincent


   1. 2012-03-12 11:31:23.508 
   /_ah/login_required?continue=https://logos-contacts.appspot.com/500 
   72138ms 0kb Mozilla/5.0 (Windows NT 5.1) AppleWebKit/534.24 (KHTML, like 
   Gecko) Chrome/11.0.696.60 Safari/534.24
   
   124.148.222.42 - - [12/Mar/2012:04:31:23 -0700] "GET 
/_ah/login_required?continue=https://logos-contacts.appspot.com/ HTTP/1.1" 500 
0 "from customer intranet" "Mozilla/5.0 (Windows NT 5.1) AppleWebKit/534.24 
(KHTML, like Gecko) Chrome/11.0.696.60 Safari/534.24" 
"logos-contacts.appspot.com" ms=72138 cpu_ms=887 api_cpu_ms=0 cpm_usd=0.024681 
loading_request=1 exit_code=104 
instance=00c61b117c5f903ba6921dbd52f633545a72631c 

   
   2. W2012-03-12 11:31:22.323
   
   Failed startup of context 
com.google.apphosting.utils.jetty.RuntimeAppEngineWebAppContext@3aa791{/,/base/data/home/apps/logos-contacts/v12.357205322028193482}
   com.google.apphosting.api.DeadlineExceededException: This request 
(0746107fc018dfa5) started at 2012/03/12 11:30:21.209 UTC and was still 
executing at 2012/03/12 11:31:21.935 UTC.
at java.util.zip.ZipFile.open(Native Method)
at java.util.zip.ZipFile.(ZipFile.java:143)
at java.util.jar.JarFile.(JarFile.java:150)
at java.util.jar.JarFile.(JarFile.java:87)
at sun.misc.URLClassPath$JarLoader.getJarFile(URLClassPath.java:919)
at sun.misc.URLClassPath$JarLoader.access$900(URLClassPath.java:723)
at sun.misc.URLClassPath$JarLoader$1.run(URLClassPath.java:854)
at java.security.AccessController.doPrivileged(Native Method)
at 
sun.misc.URLClassPath$JarLoader.ensureOpenSynchronized(URLClassPath.java:846)
at sun.misc.URLClassPath$JarLoader.ensureOpen(URLClassPath.java:838)
at sun.misc.URLClassPath$JarLoader.(URLClassPath.java:785)
at sun.misc.URLClassPath$JarLoader.(URLClassPath.java:743)
at sun.misc.URLClassPath$3.run(URLClassPath.java:412)
at java.security.AccessController.doPrivileged(Native Method)
at sun.misc.URLClassPath.getLoader(URLClassPath.java:395)
at sun.misc.URLClassPath.getLoader(URLClassPath.java:371)
at sun.misc.URLClassPath.findResource(URLClassPath.java:201)
at java.net.URLClassLoader$2.run(URLClassLoader.java:379)
at java.security.AccessController.doPrivileged(Native Method)
at java.net.URLClassLoader.findResource(URLClassLoader.java:376)
at 
com.google.apphosting.runtime.security.UserClassLoader.findResource(UserClassLoader.java:723)
at java.lang.ClassLoader.getResource(ClassLoader.java:977)
at org.mortbay.resource.Resource.newSystemResource(Resource.java:203)
at 
org.mortbay.jetty.webapp.WebXmlConfiguration.configureDefaults(WebXmlConfiguration.java:159)
at 
org.mortbay.jetty.webapp.WebAppContext.startContext(WebAppContext.java:1230)
at 
org.mortbay.jetty.handler.ContextHandler.doStart(ContextHandler.java:517)
at 
org.mortbay.jetty.webapp.WebAppContext.doStart(WebAppContext.java:467)
at 
org.mortbay.component.AbstractLifeCycle.start(AbstractLifeCycle.java:50)
at 
com.google.apphosting.runtime.jetty.AppVersionHandlerMap.createHandler(AppVersionHandlerMap.java:202)
at 
com.google.apphosting.runtime.jetty.AppVersionHandlerMap.getHandler(AppVersionHandlerMap.java:171)
at 
com.google.apphosting.runtime.jetty.JettyServletEngineAdapter.serviceRequest(JettyServletEngineAdapter.java:123)
at 
com.google.apphosting.runtime.JavaRuntime$RequestRunnable.run(JavaRuntime.java:422)
at 
com.google.tracing.TraceContext$TraceContextRunnable.runInContext(TraceContext.java:449)
at 
com.google.tracing.TraceContext$TraceContextRunnable$1.run(TraceContext.java:455)
at com.google.tracing.TraceContext.runInContext(TraceContext.java:695)
at 
com.google.tracing.TraceContext$AbstractTraceContextCallback.runInInheritedContextNoUnref(TraceContext.java:333)
at 
com.google.tracing.TraceContext$AbstractTraceContextCallback.runInInheritedContext(TraceContext.java:325)
at 
com.google.tracing.TraceContext$TraceContextRunnable.run(TraceContext.java:453)
at 
com.google.apphosting.runtime.ThreadGroupPool$PoolEntry.run(ThreadGroupPool.java:251)
at java.lang.Thread.run(Thread.java:679)
   
   3. C2012-03-12 11:31:22.345
   
   Uncaught exception from servlet
   javax.servlet.UnavailableException: Initialization failed.
at 
com.google.apphosting.runtime.jetty.AppVersionHandlerMap.createHandler(AppVersionHandlerMap.java:211)
at 
com.google.apphosting.runtime.jetty.AppVersionHandlerMap.getHandler(AppVersionHandlerMap.java:171)
at 
com.google.apphost

[google-appengine] Re: Outages?

[Admin]

Our app id: reportingsuiteengine
Master/slave
Current instances in dashboard: 8-10
Usual instances: 2-3 

Since last Thursday, without having made any kind of change either in the 
application configuration (in the console) or the actual code 
(deployments), we have been suffering an abnormal low performance and 
continuous errors (including 500 Server errors). 

Please find additional information, including logs and screenshots, in 
http://code.google.com/p/googleappengine/issues/detail?id=7113

We would appreciate if you could provide us with an estimate to get this 
situation solve. Our customers start to feel really upset and angry, and 
some of them have threaten us saying they will leave us if we don't solve 
this soon or at least give them an estimate resolution date/ time.

Thanks in advance,
Luis

El lunes 12 de marzo de 2012 13:17:05 UTC+1, Thomas escribió:
>
> We experience Google AppEngine having very poor performance / high 
> latency since about 2 weeks. Even the most basic requests take 1-2s, 
> going up to over 60s which is totally unacceptable from a user's point 
> of view. At the same time, about 1-2% of all requests are failing 
> (without any app-internal reason). Our paying (!) users are beginning 
> to complain and ask for a fix. Yet, we're totally dependent on 
> Google's mercy to solve this problem. 
>
> SO PLEASE GOOGLE: do something about it! 
> THANK YOU!! 
>
> appid: typescout 
>
> Regards, 
> Thomas

-- 
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/-/Gp9LqjY4P44J.
To post to this group, send email to google-appengine@googlegroups.com.
To unsubscribe from this group, send email to 
google-appengine+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/google-appengine?hl=en.

[google-appengine] I can't delete Application

[hiko]

I would like to delete an application.

Administration
=>Application Settings
   =>Disable or Delete Application
 =>You do not have sufficient privileges for this operation.

Administration
=>Permissions
  =>All the members are a developer. There is no owner.
XXX@.com — you   Developer   Active
YYY@***.com  Developer
Note: code downloads are prohibited.

-- 
You received this message because you are subscribed to the Google Groups 
"Google App Engine" group.
To post to this group, send email to google-appengine@googlegroups.com.
To unsubscribe from this group, send email to 
google-appengine+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/google-appengine?hl=en.

[google-appengine] URL fetch request size in googleaape​ngine

[learning coding]

I am doing a web application project using GWT in Eclipse.

I have a file on the client side which is to send on the
project.server and from server to external Repository.

   File   -->  Client-->Server-->Repository Iam Using default SDk -
(appengine-java-sdk-1.6.3.1- 1.6.3)

GWT-2.4.0 according to documentation 
http://code.google.com/p/googleappengine/wiki/SdkReleaseNotes
, the limit

for URL fetch request is 5Mb.

** But I cannot fetch the request more then 3.8Mb **

If i try to fetch more then 3.8 Mb then it gives me an Error.

  Cannot access http://URL: The request to API call urlfetch.Fetch()
was too large.   Can somebody explain me the reason for this.

Even i have to download the file from repository and save it on client
side.

So is there any limitaion of size to getContent of the file present in
the Repository to the server Side.?

Thanks


-- 
You received this message because you are subscribed to the Google Groups 
"Google App Engine" group.
To post to this group, send email to google-appengine@googlegroups.com.
To unsubscribe from this group, send email to 
google-appengine+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/google-appengine?hl=en.

[google-appengine] Re: Outages?

[Oliver]

Same here, I had opened an issue in 
stackoverflow: 
http://stackoverflow.com/questions/9638648/appengine-frontend-to-db-latency-temporarily-10-secs-every-20-calls

On Monday, March 12, 2012 1:17:05 PM UTC+1, Thomas wrote:
>
> We experience Google AppEngine having very poor performance / high 
> latency since about 2 weeks. Even the most basic requests take 1-2s, 
> going up to over 60s which is totally unacceptable from a user's point 
> of view. At the same time, about 1-2% of all requests are failing 
> (without any app-internal reason). Our paying (!) users are beginning 
> to complain and ask for a fix. Yet, we're totally dependent on 
> Google's mercy to solve this problem. 
>
> SO PLEASE GOOGLE: do something about it! 
> THANK YOU!! 
>
> appid: typescout 
>
> Regards, 
> Thomas

-- 
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/-/wxhOgFdm4r0J.
To post to this group, send email to google-appengine@googlegroups.com.
To unsubscribe from this group, send email to 
google-appengine+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/google-appengine?hl=en.

[google-appengine] Channel API not working in production

[praveen]

I have implement struts based chat application using channel API
trying to implement the chat application., The Sample struts chat
application works in local enviroinment .But in production
enviroinment totally it sucks.Please help

-- 
You received this message because you are subscribed to the Google Groups 
"Google App Engine" group.
To post to this group, send email to google-appengine@googlegroups.com.
To unsubscribe from this group, send email to 
google-appengine+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/google-appengine?hl=en.

[google-appengine] How to use javascript to directly interface with Google App Engine

[that an]

I'm looking for a way to use my javascript code to directly interface with 
the google app engine and with the datastore. 

I've already used the GWT/GAE Java SDK in Eclipse with varying levels of 
success, but I'm looking for a way to leverage the benefits of GAE & Google 
cloud server with the graphical UI strengths of writing javascript direct 
DOM manipulation on the client.   

Maybe I've missed something obvious, or something that is out there does 
it, but I've been searching for awhile now, and it just seems like Google 
is dancing around any direct client access to their App Engine and cloud 
datastore.  Strange, considering the GAE/GWT toolkits eventually need to 
convert python and java source into javascript.   

I've pretty much exhausted my leads so far - Any direction is greatly 
appreciated.  

-- 
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/-/I2nWnUMGVoUJ.
To post to this group, send email to google-appengine@googlegroups.com.
To unsubscribe from this group, send email to 
google-appengine+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/google-appengine?hl=en.

[google-appengine] Is it possible to query Datastore by parameter of Date?

[Tony Yang]

Dear Sir,
Would you help the issue below. Is it possible to query Datastore by
parameter of Date?

--- My code 
PersistenceManager pm = PMF.get().getPersistenceManager();
Query query = pm.newQuery(Customer.class);
Date currentDate = new Date();
Date beforeDate = new Date();
long currentdate = currentDate.getTime();
long beforedate = currentdate - 8640*5; //search data in
Customer.class within 5 days
beforeDate.setTime(beforedate);
query.setFilter("date > offsetDate"); // date is
column's name in Customer.class
query.declareParameters("Date offsetDate");
List conn = (List)
pm.newQuery(query).execute(beforeDate);

--- Error message from system is as below :

Class Date for query has not been resolved. Check the query and
any imports specification

Thanks a lot.

-- 
You received this message because you are subscribed to the Google Groups 
"Google App Engine" group.
To post to this group, send email to google-appengine@googlegroups.com.
To unsubscribe from this group, send email to 
google-appengine+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/google-appengine?hl=en.

[google-appengine] Re: 500 errors + high latency + please communicate with us

[Rafael Gutierrez]

We are having the same issue (DeadlineExceptions, InitializationExceptions, 
etc) since the last maintenance.

More than that, we have some remote units that make HTTP requests to post 
data to our application using an GPRS module.
Some of those units (more than 40) are no longer sending these requests (we 
can't even see them in the logs), meanwhile NOTHING changed in the remote 
units code (stable for over 1 year), and we verified that they still 
connecting to the GPRS carrier.

Please Google, give me some feedback... our clients are pushing us to have 
some news, and we can't even justify them the technical issues. It could 
kill our business reliability and reputation. 

App Id: innervision-ui :: Master/Slave

-- 
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/-/MAcRkfYGmOgJ.
To post to this group, send email to google-appengine@googlegroups.com.
To unsubscribe from this group, send email to 
google-appengine+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/google-appengine?hl=en.

[google-appengine] Re: How to secure the SDK

[Kaan Soral]

I don't think this is related to my question, but thanks anyway

On Tuesday, March 13, 2012 11:25:15 PM UTC+2, Ronoaldo José de Lana Pereira 
wrote:
>
> By your assumption that arbitrary code execution will affect your SDK 
> binaries (either java or python), I'am assuming that you are using Windows, 
> downloading the SDK binaries from untrusted websites or not running the MD5 
> checksums.  I suggest you to do all these: use Linux, downlaod only the 
> code from Google and never deploy untrusted jars / python code with your 
> application.
>
> Hope this helps,
>
> -Ronoaldo
>
> Em terça-feira, 13 de março de 2012 17h50min01s UTC-3, Kaan Soral escreveu:
>>
>> If the SDK is accessible to the outer world, it poses a HUGE security risk
>>
>> One can simply write a script for "Interactive 
>> Console" 
>> and steal all your code/data
>>
>> To prevent this - one may restrict access to Development Console and 
>> permit only 127.0.0.1, this can be easily done by modifying the Handlers of 
>> the Development Console
>>
>> Can you guys think of any other security holes?
>>
>> I've been meaning to ask this for a long time, but at the same time I 
>> didn't want to attract anyone to exploit these risks - but here it is anyway
>>
>

-- 
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/-/YQatENnLrUIJ.
To post to this group, send email to google-appengine@googlegroups.com.
To unsubscribe from this group, send email to 
google-appengine+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/google-appengine?hl=en.

[google-appengine] Re: How to secure the SDK

[Ronoaldo José de Lana Pereira]

By your assumption that arbitrary code execution will affect your SDK 
binaries (either java or python), I'am assuming that you are using Windows, 
downloading the SDK binaries from untrusted websites or not running the MD5 
checksums.  I suggest you to do all these: use Linux, downlaod only the 
code from Google and never deploy untrusted jars / python code with your 
application.

Hope this helps,

-Ronoaldo

Em terça-feira, 13 de março de 2012 17h50min01s UTC-3, Kaan Soral escreveu:
>
> If the SDK is accessible to the outer world, it poses a HUGE security risk
>
> One can simply write a script for "Interactive 
> Console" 
> and steal all your code/data
>
> To prevent this - one may restrict access to Development Console and 
> permit only 127.0.0.1, this can be easily done by modifying the Handlers of 
> the Development Console
>
> Can you guys think of any other security holes?
>
> I've been meaning to ask this for a long time, but at the same time I 
> didn't want to attract anyone to exploit these risks - but here it is anyway
>

-- 
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/-/3IIWLIKjUHkJ.
To post to this group, send email to google-appengine@googlegroups.com.
To unsubscribe from this group, send email to 
google-appengine+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/google-appengine?hl=en.

[google-appengine] How to secure the SDK

[Kaan Soral]

If the SDK is accessible to the outer world, it poses a HUGE security risk

One can simply write a script for "Interactive 
Console" 
and steal all your code/data

To prevent this - one may restrict access to Development Console and permit 
only 127.0.0.1, this can be easily done by modifying the Handlers of the 
Development Console

Can you guys think of any other security holes?

I've been meaning to ask this for a long time, but at the same time I 
didn't want to attract anyone to exploit these risks - but here it is anyway

-- 
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/-/5UH5lat5RvQJ.
To post to this group, send email to google-appengine@googlegroups.com.
To unsubscribe from this group, send email to 
google-appengine+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/google-appengine?hl=en.

[google-appengine] Re: Outages?

[Riley]

I just switched to HRD this morning, and while the app is at least 
accessible now, I still get "Request was aborted after waiting too long to 
attempt to service your request." every 60 seconds or so.  This is not even 
thrown as an exception or error - it's logged as Info.

This is really bad for us.  It's not that one out of every 100 users is 
getting a 500 page - it's that 1 out of every 100 things that EVERY USER 
tries to do doesn't work.  For us, that could mean that, in entering scores 
for a test, some of the students scores are not recorded.  Gah!  Not to 
mention the extra cost.


On Tuesday, March 13, 2012 2:29:40 PM UTC-5, Mauricio Aristizabal wrote:
>
> Just about every request results in 1 or more resources failing with 500, 
> and many that do finish take seconds.  Here's a sample error (I used to get 
> 202 or 203s, now just 'aborted after waiting too long...'):
>
>- 2012-03-13 11:52:37.682 */resources/styles/standard.css* 500 10636ms 
>0kb Mozilla/4.0 (compatible; MSIE 8.0; Windows NT 6.1; Trident/4.0; SLCC2; 
>.NET CLR 2.0.50727; .NET CLR 3.5.30729; .NET CLR 3.0.30729; Media Center 
> PC 
>6.0; MDDR; .NET4.0C) 
>67.49.52.74 - - [13/Mar/2012:11:52:37 -0700] "GET 
>/resources/styles/standard.css HTTP/1.1" 500 0 "
>http://www.commentous.com/f"; "Mozilla/4.0 (compatible; MSIE 8.0; 
>Windows NT 6.1; Trident/4.0; SLCC2; .NET CLR 2.0.50727; .NET CLR 
> 3.5.30729; 
>.NET CLR 3.0.30729; Media Center PC 6.0; MDDR; .NET4.0C)" "
>www.commentous.com" ms=10636 cpu_ms=0 api_cpu_ms=0 cpm_usd=0.82 
>pending_ms=10610 *I *2012-03-13 11:52:37.682 
>- Request was aborted after waiting too long to attempt to service 
>your request. 
>
> I don't know about the legal definition in SLA, but I consider my app to 
> be unusable and effectively down for the last six days or so.
>
> -Mauricio
>
>
>
>
>
> On Tuesday, March 6, 2012 1:17:37 PM UTC-8, Adam Sherman wrote:
>>
>> Am I the only one seeing short duration outages? They are being reflected 
>> at:
>>
>> http://code.google.com/status/appengine
>>
>> But I don't see anyone else complaining anywhere, so it makes me worried.
>>
>> A.
>>
>>
On Tuesday, March 13, 2012 2:29:40 PM UTC-5, Mauricio Aristizabal wrote:
>
> Just about every request results in 1 or more resources failing with 500, 
> and many that do finish take seconds.  Here's a sample error (I used to get 
> 202 or 203s, now just 'aborted after waiting too long...'):
>
>- 2012-03-13 11:52:37.682 */resources/styles/standard.css* 500 10636ms 
>0kb Mozilla/4.0 (compatible; MSIE 8.0; Windows NT 6.1; Trident/4.0; SLCC2; 
>.NET CLR 2.0.50727; .NET CLR 3.5.30729; .NET CLR 3.0.30729; Media Center 
> PC 
>6.0; MDDR; .NET4.0C) 
>67.49.52.74 - - [13/Mar/2012:11:52:37 -0700] "GET 
>/resources/styles/standard.css HTTP/1.1" 500 0 "
>http://www.commentous.com/f"; "Mozilla/4.0 (compatible; MSIE 8.0; 
>Windows NT 6.1; Trident/4.0; SLCC2; .NET CLR 2.0.50727; .NET CLR 
> 3.5.30729; 
>.NET CLR 3.0.30729; Media Center PC 6.0; MDDR; .NET4.0C)" "
>www.commentous.com" ms=10636 cpu_ms=0 api_cpu_ms=0 cpm_usd=0.82 
>pending_ms=10610 *I *2012-03-13 11:52:37.682 
>- Request was aborted after waiting too long to attempt to service 
>your request. 
>
> I don't know about the legal definition in SLA, but I consider my app to 
> be unusable and effectively down for the last six days or so.
>
> -Mauricio
>
>
>
>
>
> On Tuesday, March 6, 2012 1:17:37 PM UTC-8, Adam Sherman wrote:
>>
>> Am I the only one seeing short duration outages? They are being reflected 
>> at:
>>
>> http://code.google.com/status/appengine
>>
>> But I don't see anyone else complaining anywhere, so it makes me worried.
>>
>> A.
>>
>>
On Tuesday, March 13, 2012 2:29:40 PM UTC-5, Mauricio Aristizabal wrote:
>
> Just about every request results in 1 or more resources failing with 500, 
> and many that do finish take seconds.  Here's a sample error (I used to get 
> 202 or 203s, now just 'aborted after waiting too long...'):
>
>- 2012-03-13 11:52:37.682 */resources/styles/standard.css* 500 10636ms 
>0kb Mozilla/4.0 (compatible; MSIE 8.0; Windows NT 6.1; Trident/4.0; SLCC2; 
>.NET CLR 2.0.50727; .NET CLR 3.5.30729; .NET CLR 3.0.30729; Media Center 
> PC 
>6.0; MDDR; .NET4.0C) 
>67.49.52.74 - - [13/Mar/2012:11:52:37 -0700] "GET 
>/resources/styles/standard.css HTTP/1.1" 500 0 "
>http://www.commentous.com/f"; "Mozilla/4.0 (compatible; MSIE 8.0; 
>Windows NT 6.1; Trident/4.0; SLCC2; .NET CLR 2.0.50727; .NET CLR 
> 3.5.30729; 
>.NET CLR 3.0.30729; Media Center PC 6.0; MDDR; .NET4.0C)" "
>www.commentous.com" ms=10636 cpu_ms=0 api_cpu_ms=0 cpm_usd=0.82 
>pending_ms=10610 *I *2012-03-13 11:52:37.682 
>- Request was aborted after waiting too long to attempt to service 
>your request. 
>
> I don't know about the legal definition in SLA, but I consider my app to 
> be unusable and effectively down for the last six da

RE: [google-appengine] Re: Outages?

[Brandon Wirtz]

We have noticed that many of the downtimes Pingdom reports are the result of
AppsForDomains.  If you hit your app from another app, or via AOL, or
another provider that has a peering arrangement with AppEngine it will be
up.

I'm calling this AppsForDomains issues because typically during these
outages we get error pages in AppsforDomains admin pages.

In these instances Green Checks will show in the status for Appengine. But
your app will fail to resolve.

 

 

 

From: google-appengine@googlegroups.com
[mailto:google-appengine@googlegroups.com] On Behalf Of Rick Mangi
Sent: Tuesday, March 13, 2012 12:06 PM
To: google-appengine@googlegroups.com
Subject: [google-appengine] Re: Outages?

 

Same here. I use pingdom to monitor my site and it's been down on and off
for the past 24 hours to the tune of around 30 minutes.

 

I opened an enterprise support ticket but haven't heard anything back.

-- 
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/-/TAjLzJanor4J.
To post to this group, send email to google-appengine@googlegroups.com.
To unsubscribe from this group, send email to
google-appengine+unsubscr...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/google-appengine?hl=en.

-- 
You received this message because you are subscribed to the Google Groups 
"Google App Engine" group.
To post to this group, send email to google-appengine@googlegroups.com.
To unsubscribe from this group, send email to 
google-appengine+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/google-appengine?hl=en.

[google-appengine] Re: Index stuck in "building" state

[Matt Burns]

Oh, it's working now.

If someone out there fixed it, thanks.

(If it was just slow, that seems strange as it was stuck for at least an 
hour. There are only a few thousand entities in that index, I have other 
indexes that point to tens of millions and finish within an hour...)

On Tuesday, 13 March 2012 16:47:18 UTC, Matt Burns wrote:
>
> Hello,
>
> One of my indexes is stuck on the "building" state. I am unable to delete 
> it with the normal "vacuum_indexes". It is not a large entity, nor an 
> exploding index.
>
> I've seen that many others have had this bug happen to them in the past, 
> and the someone from Google has had to force the index into an error state 
> in order to vacuum it.
> Could this please be done for my index?
>
> My app id is "thestolencamerafinder" and the index that is stuck is the 
> one for the entity "SCFUser" (please don't touch my other indexes!)
>
> Cheers,
>
> Matt
>

-- 
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/-/jBu7K_iTVk4J.
To post to this group, send email to google-appengine@googlegroups.com.
To unsubscribe from this group, send email to 
google-appengine+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/google-appengine?hl=en.

[google-appengine] Re: Outages?

[Mauricio Aristizabal]

Just about every request results in 1 or more resources failing with 500, 
and many that do finish take seconds.  Here's a sample error (I used to get 
202 or 203s, now just 'aborted after waiting too long...'):

   - 2012-03-13 11:52:37.682 */resources/styles/standard.css* 500 10636ms 
   0kb Mozilla/4.0 (compatible; MSIE 8.0; Windows NT 6.1; Trident/4.0; SLCC2; 
   .NET CLR 2.0.50727; .NET CLR 3.5.30729; .NET CLR 3.0.30729; Media Center PC 
   6.0; MDDR; .NET4.0C) 
   67.49.52.74 - - [13/Mar/2012:11:52:37 -0700] "GET 
   /resources/styles/standard.css HTTP/1.1" 500 0 
   "http://www.commentous.com/f"; "Mozilla/4.0 (compatible; MSIE 8.0; Windows 
   NT 6.1; Trident/4.0; SLCC2; .NET CLR 2.0.50727; .NET CLR 3.5.30729; .NET 
   CLR 3.0.30729; Media Center PC 6.0; MDDR; .NET4.0C)" "www.commentous.com" 
   ms=10636 cpu_ms=0 api_cpu_ms=0 cpm_usd=0.82 pending_ms=10610 *I 
*2012-03-13 
   11:52:37.682 
   - Request was aborted after waiting too long to attempt to service your 
   request. 

I don't know about the legal definition in SLA, but I consider my app to be 
unusable and effectively down for the last six days or so.

-Mauricio





On Tuesday, March 6, 2012 1:17:37 PM UTC-8, Adam Sherman wrote:
>
> Am I the only one seeing short duration outages? They are being reflected 
> at:
>
> http://code.google.com/status/appengine
>
> But I don't see anyone else complaining anywhere, so it makes me worried.
>
> A.
>
>

-- 
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/-/rqPMbfROuFQJ.
To post to this group, send email to google-appengine@googlegroups.com.
To unsubscribe from this group, send email to 
google-appengine+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/google-appengine?hl=en.

[google-appengine] Re: 1:1 with a member of the App Engine community: Robert Kluin

[Kaan Soral]

I'm a big fan of robertk, loved the interview

On Tuesday, March 13, 2012 12:13:25 AM UTC+2, Johan Euphrosine (Google) 
wrote:
>
> FYI,
>
> I just posted an interview with our very Robert Kluin to Google+:
> https://plus.google.com/111042085517496880918/posts/8CHm8KKqXWU
>
> Feel free to comment there.
> -- 
> Johan Euphrosine (proppy)
> Developer Programs Engineer
> Google Developer Relations
>
>

-- 
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/-/BjsPhqc6ZNsJ.
To post to this group, send email to google-appengine@googlegroups.com.
To unsubscribe from this group, send email to 
google-appengine+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/google-appengine?hl=en.

[google-appengine] Re: Outages?

[Rick Mangi]

Same here. I use pingdom to monitor my site and it's been down on and off 
for the past 24 hours to the tune of around 30 minutes.

I opened an enterprise support ticket but haven't heard anything back.

-- 
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/-/TAjLzJanor4J.
To post to this group, send email to google-appengine@googlegroups.com.
To unsubscribe from this group, send email to 
google-appengine+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/google-appengine?hl=en.

Re: [google-appengine] Re: Lots of HTTP 500 errors and all instances restarted by GAE!

[Naresh Talluri]

Me too facing the same issue, my app id is *beta-sb*
*
*Thanks,
Naresh T


On Tue, Mar 13, 2012 at 10:15 PM, Mos  wrote:

> This seems to be the issue:
>
> http://code.google.com/p/googleappengine/issues/detail?id=7133
>
> Please vote for it 
>
>
> On Tue, Mar 13, 2012 at 5:38 PM, Mark  wrote:
>
>> This is happening to me too.  Instances getting restarted, and requests
>> taking way longer than usual.  Getting emails from unhappy users.
>>
>> My app id is bedbuzzserver, on HR ( & Java)
>>
>> --
>> 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/-/gX9u1do57t0J.
>>
>> To post to this group, send email to google-appengine@googlegroups.com.
>> To unsubscribe from this group, send email to
>> google-appengine+unsubscr...@googlegroups.com.
>> For more options, visit this group at
>> http://groups.google.com/group/google-appengine?hl=en.
>>
>
>  --
> You received this message because you are subscribed to the Google Groups
> "Google App Engine" group.
> To post to this group, send email to google-appengine@googlegroups.com.
> To unsubscribe from this group, send email to
> google-appengine+unsubscr...@googlegroups.com.
> For more options, visit this group at
> http://groups.google.com/group/google-appengine?hl=en.
>

-- 
You received this message because you are subscribed to the Google Groups 
"Google App Engine" group.
To post to this group, send email to google-appengine@googlegroups.com.
To unsubscribe from this group, send email to 
google-appengine+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/google-appengine?hl=en.

[google-appengine] Re: 1:1 with a member of the App Engine community: Robert Kluin

[stevep]

Thanks Robert. I try to use tasks as much as possible, but your ending
note will have me re-double my effort. -stevep

On Mar 12, 6:42 pm, alex  wrote:
> Please, don't just count the number of messages. Otherwise, you'll end up
> counting mermaid costumes :)
>
> On Monday, March 12, 2012 11:13:25 PM UTC+1, Johan Euphrosine (Google)
> wrote:
>
>
>
>
>
>
>
>
>
> > FYI,
>
> > I just posted an interview with our very Robert Kluin to Google+:
> >https://plus.google.com/111042085517496880918/posts/8CHm8KKqXWU
>
> > Feel free to comment there.
> > --
> > Johan Euphrosine (proppy)
> > Developer Programs Engineer
> > Google Developer Relations

-- 
You received this message because you are subscribed to the Google Groups 
"Google App Engine" group.
To post to this group, send email to google-appengine@googlegroups.com.
To unsubscribe from this group, send email to 
google-appengine+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/google-appengine?hl=en.

[google-appengine] Index stuck in "building" state

[Matt Burns]

Hello,

One of my indexes is stuck on the "building" state. I am unable to delete 
it with the normal "vacuum_indexes". It is not a large entity, nor an 
exploding index.

I've seen that many others have had this bug happen to them in the past, 
and the someone from Google has had to force the index into an error state 
in order to vacuum it.
Could this please be done for my index?

My app id is "thestolencamerafinder" and the index that is stuck is the one 
for the entity "SCFUser" (please don't touch my other indexes!)

Cheers,

Matt

-- 
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/-/ZaflLjkbP14J.
To post to this group, send email to google-appengine@googlegroups.com.
To unsubscribe from this group, send email to 
google-appengine+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/google-appengine?hl=en.

Re: [google-appengine] Re: Lots of HTTP 500 errors and all instances restarted by GAE!

[Mos]

This seems to be the issue:

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

Please vote for it 

On Tue, Mar 13, 2012 at 5:38 PM, Mark  wrote:

> This is happening to me too.  Instances getting restarted, and requests
> taking way longer than usual.  Getting emails from unhappy users.
>
> My app id is bedbuzzserver, on HR ( & Java)
>
> --
> 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/-/gX9u1do57t0J.
>
> To post to this group, send email to google-appengine@googlegroups.com.
> To unsubscribe from this group, send email to
> google-appengine+unsubscr...@googlegroups.com.
> For more options, visit this group at
> http://groups.google.com/group/google-appengine?hl=en.
>

-- 
You received this message because you are subscribed to the Google Groups 
"Google App Engine" group.
To post to this group, send email to google-appengine@googlegroups.com.
To unsubscribe from this group, send email to 
google-appengine+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/google-appengine?hl=en.

[google-appengine] Re: Lots of HTTP 500 errors and all instances restarted by GAE!

[Mark]

This is happening to me too.  Instances getting restarted, and requests 
taking way longer than usual.  Getting emails from unhappy users.

My app id is bedbuzzserver, on HR ( & Java) 

-- 
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/-/gX9u1do57t0J.
To post to this group, send email to google-appengine@googlegroups.com.
To unsubscribe from this group, send email to 
google-appengine+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/google-appengine?hl=en.

[google-appengine] Re: Lots of HTTP 500 errors and all instances restarted by GAE!

[Carter]

We too are getting lots of 500s.

Example below:
2012-03-13 09:20:56.381
Failed startup of context
com.google.apphosting.utils.jetty.RuntimeAppEngineWebAppContext@1abcd9b{/,/
base/data/home/apps/s~camiologger/1.357444708065977584}
org.mortbay.util.MultiException[java.lang.NullPointerException,
com.google.apphosting.runtime.HardDeadlineExceededError: This request
(059f3b5658365659) started at 2012/03/13 16:19:07.260 UTC and was
still executing at 2012/03/13 16:20:08.115 UTC.]
at
org.mortbay.jetty.servlet.ServletHandler.initialize(ServletHandler.java:
656)
at org.mortbay.jetty.servlet.Context.startContext(Context.java:140)
at
org.mortbay.jetty.webapp.WebAppContext.startContext(WebAppContext.java:
1250)
at
org.mortbay.jetty.handler.ContextHandler.doStart(ContextHandler.java:
517)
at org.mortbay.jetty.webapp.WebAppContext.doStart(WebAppContext.java:
467)
at
org.mortbay.component.AbstractLifeCycle.start(AbstractLifeCycle.java:
50)
at
com.google.apphosting.runtime.jetty.AppVersionHandlerMap.createHandler(AppVersionHandlerMap.java:
202)
at
com.google.apphosting.runtime.jetty.AppVersionHandlerMap.getHandler(AppVersionHandlerMap.java:
171)
at
com.google.apphosting.runtime.jetty.JettyServletEngineAdapter.serviceRequest(JettyServletEngineAdapter.java:
123)
at com.google.apphosting.runtime.JavaRuntime
$RequestRunnable.run(JavaRuntime.java:422)
at com.google.tracing.TraceContext
$TraceContextRunnable.runInContext(TraceContext.java:449)
at com.google.tracing.TraceContext$TraceContextRunnable
$1.run(TraceContext.java:455)
at com.google.tracing.TraceContext.runInContext(TraceContext.java:
695)
at com.google.tracing.TraceContext
$AbstractTraceContextCallback.runInInheritedContextNoUnref(TraceContext.java:
333)
at com.google.tracing.TraceContext
$AbstractTraceContextCallback.runInInheritedContext(TraceContext.java:
325)
at com.google.tracing.TraceContext
$TraceContextRunnable.run(TraceContext.java:453)
at com.google.apphosting.runtime.ThreadGroupPool
$PoolEntry.run(ThreadGroupPool.java:251)
at java.lang.Thread.run(Thread.java:679)
java.lang.NullPointerException
at java.lang.Class.isAssignableFrom(Native Method)
at org.mortbay.jetty.servlet.ServletHolder.doStart(ServletHolder.java:
256)
at
org.mortbay.component.AbstractLifeCycle.start(AbstractLifeCycle.java:
50)
at
org.mortbay.jetty.servlet.ServletHandler.initialize(ServletHandler.java:
685)
at org.mortbay.jetty.servlet.Context.startContext(Context.java:140)
at
org.mortbay.jetty.webapp.WebAppContext.startContext(WebAppContext.java:
1250)
at
org.mortbay.jetty.handler.ContextHandler.doStart(ContextHandler.java:
517)
at org.mortbay.jetty.webapp.WebAppContext.doStart(WebAppContext.java:
467)
at
org.mortbay.component.AbstractLifeCycle.start(AbstractLifeCycle.java:
50)
at
com.google.apphosting.runtime.jetty.AppVersionHandlerMap.createHandler(AppVersionHandlerMap.java:
202)
at
com.google.apphosting.runtime.jetty.AppVersionHandlerMap.getHandler(AppVersionHandlerMap.java:
171)
at
com.google.apphosting.runtime.jetty.JettyServletEngineAdapter.serviceRequest(JettyServletEngineAdapter.java:
123)
at com.google.apphosting.runtime.JavaRuntime
$RequestRunnable.run(JavaRuntime.java:422)
at com.google.tracing.TraceContext
$TraceContextRunnable.runInContext(TraceContext.java:449)
at com.google.tracing.TraceContext$TraceContextRunnable
$1.run(TraceContext.java:455)
at com.google.tracing.TraceContext.runInContext(TraceContext.java:
695)
at com.google.tracing.TraceContext
$AbstractTraceContextCallback.runInInheritedContextNoUnref(TraceContext.java:
333)
at com.google.tracing.TraceContext
$AbstractTraceContextCallback.runInInheritedContext(TraceContext.java:
325)
at com.google.tracing.TraceContext
$TraceContextRunnable.run(TraceContext.java:453)
at com.google.apphosting.runtime.ThreadGroupPool
$PoolEntry.run(ThreadGroupPool.java:251)
at java.lang.Thread.run(Thread.java:679)
com.google.apphosting.runtime.HardDeadlineExceededError: This request
(059f3b5658365659) started at 2012/03/13 16:19:07.260 UTC and was
still executing at 2012/03/13 16:20:08.115 UTC.
at
com.google.appengine.runtime.Request.process-059f3b5658365659(Request.java)
at java.io.FileInputStream.readBytes(Native Method)
at java.io.FileInputStream.read(FileInputStream.java:231)
at sun.misc.Resource.getBytes(Resource.java:124)
at java.net.URLClassLoader.defineClass(URLClassLoader.java:273)
at sun.reflect.GeneratedMethodAccessor6.invoke(Unknown Source)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:
43)
at java.lang.reflect.Method.invoke(Method.java:616)
at java.lang.ClassLoader.loadClass(ClassLoader.java:266)
at org

[google-appengine] Re: Lots of HTTP 500 errors and all instances restarted by GAE!

[Upscale]

Hi Takashi,

we are getting error 500 in all versions now.
Deployment is checking for finished deployment for more than 7 minutes
now.

I also have a very strange bug (java): If I remove


appstats
com.google.appengine.tools.appstats.AppstatsFilter

logMessage
Appstats available: /appstats/details?
time={ID}




appstats
/*



from web.xml, the static content is not available any more.

All of the strange errors we get seem to be linked with memcache and
appstats:

Uncaught exception from servlet
com.google.apphosting.runtime.HardDeadlineExceededError: This request
(43be6c5c78b8bbb6) started at 2012/03/13 15:36:13.367 UTC and was
still executing at 2012/03/13 15:37:14.451 UTC.
at com.google.appengine.repackaged.com.google.protobuf.Descriptors
$Descriptor.(Descriptors.java:577)
at com.google.appengine.repackaged.com.google.protobuf.Descriptors
$Descriptor.(Descriptors.java:412)
at com.google.appengine.repackaged.com.google.protobuf.Descriptors
$FileDescriptor.(Descriptors.java:342)
at com.google.appengine.repackaged.com.google.protobuf.Descriptors
$FileDescriptor.buildFrom(Descriptors.java:208)
at com.google.appengine.repackaged.com.google.protobuf.Descriptors
$FileDescriptor.internalBuildGeneratedFileFrom(Descriptors.java:271)
at
com.google.appengine.tools.appstats.StatsProtos.(StatsProtos.java:
5427)
at com.google.appengine.tools.appstats.StatsProtos
$RequestStatProto.getDescriptor(StatsProtos.java:3504)
at
com.google.appengine.tools.appstats.MemcacheWriter.persist(MemcacheWriter.java:
238)
at
com.google.appengine.tools.appstats.MemcacheWriter.commit(MemcacheWriter.java:
168)
at
com.google.appengine.tools.appstats.AppstatsFilter.doFilter(AppstatsFilter.java:
151)
at org.mortbay.jetty.servlet.ServletHandler
$CachedChain.doFilter(ServletHandler.java:1157)
at
com.google.apphosting.utils.servlet.ParseBlobUploadFilter.doFilter(ParseBlobUploadFilter.java:
102)
at org.mortbay.jetty.servlet.ServletHandler
$CachedChain.doFilter(ServletHandler.java:1157)
at
com.google.apphosting.runtime.jetty.SaveSessionFilter.doFilter(SaveSessionFilter.java:
35)

Do you have a resolution for the problem?

Greetings
upscale

-- 
You received this message because you are subscribed to the Google Groups 
"Google App Engine" group.
To post to this group, send email to google-appengine@googlegroups.com.
To unsubscribe from this group, send email to 
google-appengine+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/google-appengine?hl=en.

[google-appengine] Re: Re: Messages not delivered using Mail API

[Alexis]

app-id; fp-spalife

I opened a ticket for this:
http://code.google.com/p/googleappengine/issues/detail?id=7124 

Thanks

-- 
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/-/BoXkLQBfctkJ.
To post to this group, send email to google-appengine@googlegroups.com.
To unsubscribe from this group, send email to 
google-appengine+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/google-appengine?hl=en.

Re: [google-appengine] Lots of HTTP 500 errors and all instances restarted by GAE!

[Hamish]

Hi,

I will email the app id rather than post it on this public forum.

We are still seeing HTTP 500 errors today. Instances seem to take a long 
time to come up.

We are using HR datastore.

Tanks,
Hamish


On Friday, March 9, 2012 7:00:57 PM UTC, Takashi Matsuo (Google) wrote:
>
>
> Hi Hamish,
>
> Could you give me your app-id?
>
> On Fri, Mar 9, 2012 at 12:44 AM, Hamish  wrote:
>
>> Hi,
>>
>> We use GAE to host one of our Java apps. Recently we have been 
>> experiencing quite a lot of HTTP 500 errors and timeouts from App Engine. 
>> It appears that App Engine sometimes restarts all of our instances at the 
>> same time and does not wait for instances to finish serving requests.  See 
>> the attached images:
>>
>>
>> 
>>
>>
>> 
>>
>>
>>
>>  In the logs I see a lot of entries like this:
>>
>> "Request was aborted after waiting too long to attempt to service your 
>> request."
>>
>> The request time shown in the logs was typically around 10,000ms before 
>> the request was terminated.
>>
>> The screenshots were taken at 23.45 GMT on 1 March. We have since 
>> experienced similar issues. The latest being yesterday afternoon at 15.30 
>> GMT. The one yesterday was very odd. It appears that the graphs in the 
>> dashboard all got reset when the instances restarted as if the entire app 
>> had been redeployed with no history at all.
>>
>> So my questions:
>>
>> 1) Can someone in Google please look into this for me?
>> 2) Why would all instances be restarted at the same time?
>> 3) Why wouldn't App Engine let the instances finish serving requests 
>> before restarting?
>> 4) Is there any way I can elavate this issue?
>> 5) Is there a better place to report this issue so someone in Google will 
>> investigate?
>>
>> This is very serious and we need to get to the bottom of it. 
>>
>> Thanks,
>> Hamish
>>
>>
>>
>>  -- 
>> 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/-/E2c_GofputsJ.
>> To post to this group, send email to google-appengine@googlegroups.com.
>> To unsubscribe from this group, send email to 
>> google-appengine+unsubscr...@googlegroups.com.
>> For more options, visit this group at 
>> http://groups.google.com/group/google-appengine?hl=en.
>>
>
>
>
> -- 
> Takashi Matsuo | Developer Advocate | tmat...@google.com | 03-6384-9224
>  

-- 
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/-/hJVrvaRZi58J.
To post to this group, send email to google-appengine@googlegroups.com.
To unsubscribe from this group, send email to 
google-appengine+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/google-appengine?hl=en.

[google-appengine] Re: Outages?

[Sekhar]

Same here...a flurry of errors. The last one:


   1. 
   E2012-03-13 08:42:46.475
   
   org.datanucleus.transaction.Transaction commit: Operation commit failed on 
resource: org.datanucleus.store.appengine.DatastoreXAResource@1389244, error 
code UNKNOWN and transaction: [DataNucleus Transaction, ID=Xid=
   
   

On Tuesday, March 6, 2012 1:17:37 PM UTC-8, Adam Sherman wrote:
>
> Am I the only one seeing short duration outages? They are being reflected 
> at:
>
> http://code.google.com/status/appengine
>
> But I don't see anyone else complaining anywhere, so it makes me worried.
>
> A.
>
>

-- 
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/-/pzHNncNLG3wJ.
To post to this group, send email to google-appengine@googlegroups.com.
To unsubscribe from this group, send email to 
google-appengine+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/google-appengine?hl=en.

Re: [google-appengine] Re: paid user, email delivered, but can't be received

[Jonathan]

Thanks for asking but NOT at all.


On Monday, March 12, 2012 11:28:42 AM UTC+2, Paco Paco wrote:
>
> Jonathan, have you found a solution yet?
>
> On Sat, Mar 10, 2012 at 12:47 AM, Jonathan wrote:
>
>> I've exactly the same problem, after the first 100 recipients the 
>> delivery is blocked. After 24hours there is a reset , and so on. 
>> I have 10$/day budget but it does not help.
>>  
>>
>> On Thursday, March 8, 2012 5:11:38 AM UTC+2, Paco Paco wrote: 
>>>
>>> The first charge was cleared, and 5000 emails are definitely within 
>>> the quota, and I can see that on the dashboard. 
>>> The first 100 recipients had received my email, but after the first 
>>> 100, nobody had received anything. 
>>> What am I supposed to do?
>>
>> -- 
>> 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/-/kuEWOszJjAQJ. 
>>
>> To post to this group, send email to google-appengine@googlegroups.com.
>> To unsubscribe from this group, send email to 
>> google-appengine+unsubscr...@googlegroups.com.
>> For more options, visit this group at 
>> http://groups.google.com/group/google-appengine?hl=en.
>>
>
>
On Monday, March 12, 2012 11:28:42 AM UTC+2, Paco Paco wrote:
>
> Jonathan, have you found a solution yet?
>
> On Sat, Mar 10, 2012 at 12:47 AM, Jonathan wrote:
>
>> I've exactly the same problem, after the first 100 recipients the 
>> delivery is blocked. After 24hours there is a reset , and so on. 
>> I have 10$/day budget but it does not help.
>>  
>>
>> On Thursday, March 8, 2012 5:11:38 AM UTC+2, Paco Paco wrote: 
>>>
>>> The first charge was cleared, and 5000 emails are definitely within 
>>> the quota, and I can see that on the dashboard. 
>>> The first 100 recipients had received my email, but after the first 
>>> 100, nobody had received anything. 
>>> What am I supposed to do?
>>
>> -- 
>> 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/-/kuEWOszJjAQJ. 
>>
>> To post to this group, send email to google-appengine@googlegroups.com.
>> To unsubscribe from this group, send email to 
>> google-appengine+unsubscr...@googlegroups.com.
>> For more options, visit this group at 
>> http://groups.google.com/group/google-appengine?hl=en.
>>
>
>
On Monday, March 12, 2012 11:28:42 AM UTC+2, Paco Paco wrote:
>
> Jonathan, have you found a solution yet?
>
> On Sat, Mar 10, 2012 at 12:47 AM, Jonathan wrote:
>
>> I've exactly the same problem, after the first 100 recipients the 
>> delivery is blocked. After 24hours there is a reset , and so on. 
>> I have 10$/day budget but it does not help.
>>  
>>
>> On Thursday, March 8, 2012 5:11:38 AM UTC+2, Paco Paco wrote: 
>>>
>>> The first charge was cleared, and 5000 emails are definitely within 
>>> the quota, and I can see that on the dashboard. 
>>> The first 100 recipients had received my email, but after the first 
>>> 100, nobody had received anything. 
>>> What am I supposed to do?
>>
>> -- 
>> 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/-/kuEWOszJjAQJ. 
>>
>> To post to this group, send email to google-appengine@googlegroups.com.
>> To unsubscribe from this group, send email to 
>> google-appengine+unsubscr...@googlegroups.com.
>> For more options, visit this group at 
>> http://groups.google.com/group/google-appengine?hl=en.
>>
>
>

-- 
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/-/Wswe00L_dtMJ.
To post to this group, send email to google-appengine@googlegroups.com.
To unsubscribe from this group, send email to 
google-appengine+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/google-appengine?hl=en.

Re: [google-appengine] Re: Outages?

[Mark]

>
> I have had outages throughout this morning.  
>

  My app is bedbuzzserver.appspot.com, Java app on HR.

  From 2am until 7.48am.  I have filed Production issue 7138.

  My instances keep getting reset (and then taking too long to start up), & 
my '*Current Load' *logs get reset to 0 
(e.g. bedbuzzserver.appspot.com/logon goes from 100 calls today, to 0)

-- 
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/-/mRSLiWjZgc0J.
To post to this group, send email to google-appengine@googlegroups.com.
To unsubscribe from this group, send email to 
google-appengine+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/google-appengine?hl=en.

[google-appengine] Re: Outages?

[tempy]

To chime in: My HR app is also very unstable for what seems to be the
last few weeks. Sometimes it performs fine, and sometimes its spinning
up unnecessary instances and not using them, throwing deadlineexceeded
errors, killing requests after a long wait with "Request was aborted
after waiting too long to attempt to service your request." and on and
on - all under a light load.

Its especially galling when GAE errors result in the user seeing a
Google-branded error page, see here:
http://code.google.com/p/googleappengine/issues/detail?id=6965

All the suggestions that this is somehow isolated to the MS datastore
seem particularly disingenuous to my ears right now. For many months I
am totally happy with GAE and recommend it to everyone - then I have a
few weeks like this and I start to lay serious plans for extricating
myself from this platform. I have no idea if my SLA has been violated
as per all the legal definitions, but it sure feels like it.

On Mar 13, 3:29 pm, Johan Euphrosine  wrote:
> Thanks mos,
>
> I asked for more detail on the tickets, let's followup there.
>
> App Engine is indeed out of beta and now covered by an SLA for paid
> application.
>
> If you feel that the SLA for your application has been violated, please
> consider the form linked there to request 
> credit:http://code.google.com/appengine/sla.html
>
>
>
>
>
>
>
>
>
> On Tue, Mar 13, 2012 at 3:22 PM, Mos  wrote:
> > > What is your application id?
>
> > krisen-talk    (www.krisentalk.de)
>
> > > Feel free to open a production issue
>
> > There is already an issue from someone else (following this thread a lot
> > of people are affected):
>
> >http://code.google.com/p/googleappengine/issues/detail?id=7133
>
> > Johan, what's going on with GAE the last days?  It doesn't feel like a
> > PaaS in production mode.
> > Perhaps Google should reintroduce the Beta status. ;)
>
> > On Tue, Mar 13, 2012 at 3:10 PM, Johan Euphrosine wrote:
>
> >> What is your application id?
>
> >> Feel free to open a production issue, if you want to investigate this
> >> offthread:
>
> >>http://code.google.com/p/googleappengine/issues/entry?template=Produc...
>
> >> On Tue, Mar 13, 2012 at 11:44 AM, Mos  wrote:
>
> >>> Same thing the last minutes on our app (HRD, Java, Low-Traffic, one
> >>> instance, no new deployment, simple page just hitting MemCache):
>
> >>> "Request was aborted after waiting too long to attempt to service your
> >>> request."   -->  User sees 500er
>
> >>> GAE-Team, what is going on the last days?  In my opinion the Google App
> >>> Engine is unreliable and looks more like a alpha- or beta-
> >>> cloudenvrionment
>
> >>> Please Google share you analysis with us.
>
> >>> Cheers
> >>> Mos
>
> >>> 2012/3/13 Sébastien Tromp 
>
>  Hello,
>
>  Same thing here, since around an hour ago:
>  AppID: fiveorbsgame & fiveorbsgame-test
>
>  On Tue, Mar 13, 2012 at 9:59 AM, Miroslav Genov wrote:
>
> > I'm encountering the same issue with HR app. The spike got started in
> > about ~1 hour from now.
>
> > AppID: cmsevobg
> > Datastore: HR
>
> > On Tuesday, March 13, 2012 10:36:38 AM UTC+2, Richard Watson wrote:
>
> >> In case you're keeping track of issues thinking it's generally
> >> cleared up:
>
> >> I'm on HR and have noticed higher latencies (couple seconds instead
> >> of e.g. 300ms) lately and sometimes higher error rates (a few instead 
> >> of
> >> 0-3). Yesterday over about 6 hours I got a ton of 60-second requests 
> >> that
> >> threw 500's with accompanying messages [1], usually on memcache sets
> >> hitting a deadline exceeded.  Also, over the last couple weeks I've 
> >> been
> >> running 3 instances permanently despite sometimes shutting them down
> >> manually.  Usually I get by on one just fine with bursts of 2 or 3.  
> >> I've
> >> noticed that one instance serves the majority of traffic with the 
> >> other two
> >> serving maybe 50 requests over many hours, so the shutdown isn't 
> >> aggressive
> >> enough.
>
> >> "This request caused a new process to be started for your
> >> application..."
> >> +
> >> "A problem was encountered with the process that handled this
> >> request, causing it to exit" in the same request.
>
> >> App-id: 2dumo-hr
>
> > On Tuesday, March 13, 2012 10:36:38 AM UTC+2, Richard Watson wrote:
>
> >> In case you're keeping track of issues thinking it's generally
> >> cleared up:
>
> >> I'm on HR and have noticed higher latencies (couple seconds instead
> >> of e.g. 300ms) lately and sometimes higher error rates (a few instead 
> >> of
> >> 0-3). Yesterday over about 6 hours I got a ton of 60-second requests 
> >> that
> >> threw 500's with accompanying messages [1], usually on memcache sets
> >> hitting a deadline exceeded.  Also, over the last couple weeks I've 
> >> been
> >> running 3 instances permanently despite sometimes sh

Re: [google-appengine] Re: Outages?

[Johan Euphrosine]

Thanks mos,

I asked for more detail on the tickets, let's followup there.

App Engine is indeed out of beta and now covered by an SLA for paid
application.

If you feel that the SLA for your application has been violated, please
consider the form linked there to request credit:
http://code.google.com/appengine/sla.html

On Tue, Mar 13, 2012 at 3:22 PM, Mos  wrote:

> > What is your application id?
>
> krisen-talk(www.krisentalk.de)
>
>
> > Feel free to open a production issue
>
> There is already an issue from someone else (following this thread a lot
> of people are affected):
>
> http://code.google.com/p/googleappengine/issues/detail?id=7133
>
> Johan, what's going on with GAE the last days?  It doesn't feel like a
> PaaS in production mode.
> Perhaps Google should reintroduce the Beta status. ;)
>
>
> On Tue, Mar 13, 2012 at 3:10 PM, Johan Euphrosine wrote:
>
>> What is your application id?
>>
>> Feel free to open a production issue, if you want to investigate this
>> offthread:
>>
>> http://code.google.com/p/googleappengine/issues/entry?template=Production%20issue
>>
>>
>> On Tue, Mar 13, 2012 at 11:44 AM, Mos  wrote:
>>
>>> Same thing the last minutes on our app (HRD, Java, Low-Traffic, one
>>> instance, no new deployment, simple page just hitting MemCache):
>>>
>>> "Request was aborted after waiting too long to attempt to service your
>>> request."   -->  User sees 500er
>>>
>>> GAE-Team, what is going on the last days?  In my opinion the Google App
>>> Engine is unreliable and looks more like a alpha- or beta-
>>> cloudenvrionment
>>>
>>> Please Google share you analysis with us.
>>>
>>> Cheers
>>> Mos
>>>
>>>
>>>
>>>
>>>
>>> 2012/3/13 Sébastien Tromp 
>>>
 Hello,

 Same thing here, since around an hour ago:
 AppID: fiveorbsgame & fiveorbsgame-test


 On Tue, Mar 13, 2012 at 9:59 AM, Miroslav Genov wrote:

> I'm encountering the same issue with HR app. The spike got started in
> about ~1 hour from now.
>
> AppID: cmsevobg
> Datastore: HR
>
> On Tuesday, March 13, 2012 10:36:38 AM UTC+2, Richard Watson wrote:
>>
>> In case you're keeping track of issues thinking it's generally
>> cleared up:
>>
>> I'm on HR and have noticed higher latencies (couple seconds instead
>> of e.g. 300ms) lately and sometimes higher error rates (a few instead of
>> 0-3). Yesterday over about 6 hours I got a ton of 60-second requests that
>> threw 500's with accompanying messages [1], usually on memcache sets
>> hitting a deadline exceeded.  Also, over the last couple weeks I've been
>> running 3 instances permanently despite sometimes shutting them down
>> manually.  Usually I get by on one just fine with bursts of 2 or 3.  I've
>> noticed that one instance serves the majority of traffic with the other 
>> two
>> serving maybe 50 requests over many hours, so the shutdown isn't 
>> aggressive
>> enough.
>>
>> "This request caused a new process to be started for your
>> application..."
>> +
>> "A problem was encountered with the process that handled this
>> request, causing it to exit" in the same request.
>>
>> App-id: 2dumo-hr
>>
>
> On Tuesday, March 13, 2012 10:36:38 AM UTC+2, Richard Watson wrote:
>>
>> In case you're keeping track of issues thinking it's generally
>> cleared up:
>>
>> I'm on HR and have noticed higher latencies (couple seconds instead
>> of e.g. 300ms) lately and sometimes higher error rates (a few instead of
>> 0-3). Yesterday over about 6 hours I got a ton of 60-second requests that
>> threw 500's with accompanying messages [1], usually on memcache sets
>> hitting a deadline exceeded.  Also, over the last couple weeks I've been
>> running 3 instances permanently despite sometimes shutting them down
>> manually.  Usually I get by on one just fine with bursts of 2 or 3.  I've
>> noticed that one instance serves the majority of traffic with the other 
>> two
>> serving maybe 50 requests over many hours, so the shutdown isn't 
>> aggressive
>> enough.
>>
>> "This request caused a new process to be started for your
>> application..."
>> +
>> "A problem was encountered with the process that handled this
>> request, causing it to exit" in the same request.
>>
>> App-id: 2dumo-hr
>>
>  --
> 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/-/YUHiXXkGPAgJ.
>
> To post to this group, send email to google-appengine@googlegroups.com
> .
> To unsubscribe from this group, send email to
> google-appengine+unsubscr...@googlegroups.com.
> For more options, visit this group at
> http://groups.google.com/group/google-appengine?hl=en.
>

  --
>>>

Re: [google-appengine] Re: Outages?

[Riley Eynon-Lynch]

We migrated our app to the HRD last night. With 4 GB of data quota in
around 2M entities it took 20-30 minutes.  On the new app, we are seeing
response times at about 1% of the MS app - 100 times faster.  Our app was
read only for less than three seconds - enough to affect 10 requests from 2
users.

We decided to do this without a very thorough testing because the app was
broken across all of our users on M/S, and will only break in a small
percentage of users on HRD.  When it does break, it will be pretty
harmless, and we expect to fix the inconsistency problems by the end of
today.  We just could not wait until Monday for a possible fix for the MS
app.

If you've got a similar setup or similar needs, I recommend a
hastier-than-usual switch. Just watch out for the email limits~

On Tue, Mar 13, 2012 at 9:04 AM, Johan Euphrosine  wrote:

> If you are not using the datastore it should be trivial to move your
> application to the new HRD infrastructure.
>
> If you don't need the same appid, just create a new HRD application and
> deploy your code on it.
>
> If you need the same appid, use the self migration tool:
> https://appengine.google.com/migrating?app_id=
>
> Feel free to open a production ticket if you need any assistance migrating
> your application:
>
> http://code.google.com/p/googleappengine/issues/entry?template=Production%20issue
>
>
> On Tue, Mar 13, 2012 at 12:44 PM, charisl  wrote:
>
>> Hello Ikai
>>
>> our app is *betscoreslive*. In our settings master/slave replication is
>> activated but we are NOT using the datastore at all and we have been
>> experiencing the DeadlineExceedExceptions and increased instance number
>> mentioned by the rest of the people in the discussion. Our app is only
>> using memcache.
>>
>> Normal operation
>> during traffic peaks: instances ~25, ~45 requests/second and QPS > 1
>>
>> Now we observe: 12 instances doing nth with ~2 requests/second and QPS 0.2
>> We had the Deadline exceptions since one week now with small periods of
>> normal operation. During the problematic periods, our app is pretty
>> unresponsive.
>>
>> Will the announced maintenance for master/slave apps will solve the issue
>> for our app as well?
>>
>> thanks in advance
>>
>> Charis
>>
>> On Friday, March 9, 2012 9:15:35 PM UTC+2, Ikai Lan wrote:
>>>
>>> Hey everyone,
>>>
>>> Here are a few things that will help:
>>>
>>> 1. Application IDs (<--- if you have nothing else, at least provide this)
>>> 2. What is your QPS?
>>> 3. What % of your requests are errors?
>>>
>>> --
>>> Ikai Lan
>>> Developer Programs Engineer, Google App Engine
>>> plus.ikailan.com
>>>
>>>
>>>
>>> On Fri, Mar 9, 2012 at 7:24 AM, Ronoaldo José de Lana Pereira <
>>> rpere...@beneficiofacil.com.**br >wrote:
>>>
 +1 for seeing the same problems on my app.

 It started to be worse after maintenance on March 7.

 Em sexta-feira, 9 de março de 2012 08h33min36s UTC-3, Nikolai escreveu:

> +1
> we had to move to our backup systems. Everything is full of 500 errors
> or hardcore latency.
> Most of the 500 errors we see aren't even logged so this seems to be a
> goole problem one abstraction layer above the app.
>
> And yes - sometimes we have got the same feeling, that we are the only
> ones that use appengine in a production setting. You are not alone ;)
>
> regards,
> nikolai
>
> Am Dienstag, 6. März 2012 22:17:37 UTC+1 schrieb Adam Sherman:
>>
>> Am I the only one seeing short duration outages? They are being
>> reflected at:
>>
>> http://code.google.com/status/appengine
>>
>> But I don't see anyone else complaining anywhere, so it makes me
>> worried.
>>
>> A.
>>
>>  --
 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/-/**yixu1yAlMs4J
 .

 To post to this group, send email to google-appengine@googlegroups.**
 com .
 To unsubscribe from this group, send email to
 google-appengine+unsubscribe@**googlegroups.com
 .
 For more options, visit this group at http://groups.google.com/**
 group/google-appengine?hl=en
 .

>>>
>>>  --
>> 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/-/W1KVvW7v-SEJ.
>>
>> To post to this group, send email to google-appengine@googlegroups.com.
>> To unsubscribe from this group, send email to
>> google-appengine+unsubscr...@googlegroups.com.
>> For more options, visit this group at
>> http://groups.google.com/group/google-appengine?hl=en.
>>
>
>
>
> --
> Johan Euphrosine

Re: [google-appengine] Re: Outages?

[Mos]

> What is your application id?

krisen-talk(www.krisentalk.de)

> Feel free to open a production issue

There is already an issue from someone else (following this thread a lot of
people are affected):

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

Johan, what's going on with GAE the last days?  It doesn't feel like a PaaS
in production mode.
Perhaps Google should reintroduce the Beta status. ;)


On Tue, Mar 13, 2012 at 3:10 PM, Johan Euphrosine  wrote:

> What is your application id?
>
> Feel free to open a production issue, if you want to investigate this
> offthread:
>
> http://code.google.com/p/googleappengine/issues/entry?template=Production%20issue
>
>
> On Tue, Mar 13, 2012 at 11:44 AM, Mos  wrote:
>
>> Same thing the last minutes on our app (HRD, Java, Low-Traffic, one
>> instance, no new deployment, simple page just hitting MemCache):
>>
>> "Request was aborted after waiting too long to attempt to service your
>> request."   -->  User sees 500er
>>
>> GAE-Team, what is going on the last days?  In my opinion the Google App
>> Engine is unreliable and looks more like a alpha- or beta-
>> cloudenvrionment
>>
>> Please Google share you analysis with us.
>>
>> Cheers
>> Mos
>>
>>
>>
>>
>>
>> 2012/3/13 Sébastien Tromp 
>>
>>> Hello,
>>>
>>> Same thing here, since around an hour ago:
>>> AppID: fiveorbsgame & fiveorbsgame-test
>>>
>>>
>>> On Tue, Mar 13, 2012 at 9:59 AM, Miroslav Genov wrote:
>>>
 I'm encountering the same issue with HR app. The spike got started in
 about ~1 hour from now.

 AppID: cmsevobg
 Datastore: HR

 On Tuesday, March 13, 2012 10:36:38 AM UTC+2, Richard Watson wrote:
>
> In case you're keeping track of issues thinking it's generally cleared
> up:
>
> I'm on HR and have noticed higher latencies (couple seconds instead of
> e.g. 300ms) lately and sometimes higher error rates (a few instead of 
> 0-3).
> Yesterday over about 6 hours I got a ton of 60-second requests that threw
> 500's with accompanying messages [1], usually on memcache sets hitting a
> deadline exceeded.  Also, over the last couple weeks I've been running 3
> instances permanently despite sometimes shutting them down manually.
>  Usually I get by on one just fine with bursts of 2 or 3.  I've noticed
> that one instance serves the majority of traffic with the other two 
> serving
> maybe 50 requests over many hours, so the shutdown isn't aggressive 
> enough.
>
> "This request caused a new process to be started for your
> application..."
> +
> "A problem was encountered with the process that handled this request,
> causing it to exit" in the same request.
>
> App-id: 2dumo-hr
>

 On Tuesday, March 13, 2012 10:36:38 AM UTC+2, Richard Watson wrote:
>
> In case you're keeping track of issues thinking it's generally cleared
> up:
>
> I'm on HR and have noticed higher latencies (couple seconds instead of
> e.g. 300ms) lately and sometimes higher error rates (a few instead of 
> 0-3).
> Yesterday over about 6 hours I got a ton of 60-second requests that threw
> 500's with accompanying messages [1], usually on memcache sets hitting a
> deadline exceeded.  Also, over the last couple weeks I've been running 3
> instances permanently despite sometimes shutting them down manually.
>  Usually I get by on one just fine with bursts of 2 or 3.  I've noticed
> that one instance serves the majority of traffic with the other two 
> serving
> maybe 50 requests over many hours, so the shutdown isn't aggressive 
> enough.
>
> "This request caused a new process to be started for your
> application..."
> +
> "A problem was encountered with the process that handled this request,
> causing it to exit" in the same request.
>
> App-id: 2dumo-hr
>
  --
 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/-/YUHiXXkGPAgJ.

 To post to this group, send email to google-appengine@googlegroups.com.
 To unsubscribe from this group, send email to
 google-appengine+unsubscr...@googlegroups.com.
 For more options, visit this group at
 http://groups.google.com/group/google-appengine?hl=en.

>>>
>>>  --
>>> You received this message because you are subscribed to the Google
>>> Groups "Google App Engine" group.
>>> To post to this group, send email to google-appengine@googlegroups.com.
>>> To unsubscribe from this group, send email to
>>> google-appengine+unsubscr...@googlegroups.com.
>>> For more options, visit this group at
>>> http://groups.google.com/group/google-appengine?hl=en.
>>>
>>
>>  --
>> You received this message because you are subscribed to the Google Groups
>> "Google App Engine" group.
>> To post

[google-appengine] Re: Unable to remove appstats (Java)

[Upscale]

bounce

-- 
You received this message because you are subscribed to the Google Groups 
"Google App Engine" group.
To post to this group, send email to google-appengine@googlegroups.com.
To unsubscribe from this group, send email to 
google-appengine+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/google-appengine?hl=en.

Re: [google-appengine] Re: Outages?

[Johan Euphrosine]

What is your application id? Did you already fill a production issue?

On Tue, Mar 13, 2012 at 3:10 PM, Jason  wrote:

> I'm using HRD and am still getting tons of 500s since early this
> morning.
>
> On Mar 13, 8:52 am, Johan Euphrosine  wrote:
> > I believe this was related to:
> http://code.google.com/p/googleappengine/issues/detail?id=7130
> >
> > This should now be fixed.
> >
> >
> >
> >
> >
> >
> >
> >
> >
> > On Tue, Mar 13, 2012 at 9:59 AM, Miroslav Genov 
> wrote:
> > > I'm encountering the same issue with HR app. The spike got started in
> > > about ~1 hour from now.
> >
> > > AppID: cmsevobg
> > > Datastore: HR
> >
> > > On Tuesday, March 13, 2012 10:36:38 AM UTC+2, Richard Watson wrote:
> >
> > >> In case you're keeping track of issues thinking it's generally
> cleared up:
> >
> > >> I'm on HR and have noticed higher latencies (couple seconds instead of
> > >> e.g. 300ms) lately and sometimes higher error rates (a few instead of
> 0-3).
> > >> Yesterday over about 6 hours I got a ton of 60-second requests that
> threw
> > >> 500's with accompanying messages [1], usually on memcache sets
> hitting a
> > >> deadline exceeded.  Also, over the last couple weeks I've been
> running 3
> > >> instances permanently despite sometimes shutting them down manually.
> > >>  Usually I get by on one just fine with bursts of 2 or 3.  I've
> noticed
> > >> that one instance serves the majority of traffic with the other two
> serving
> > >> maybe 50 requests over many hours, so the shutdown isn't aggressive
> enough.
> >
> > >> "This request caused a new process to be started for your
> application..."
> > >> +
> > >> "A problem was encountered with the process that handled this request,
> > >> causing it to exit" in the same request.
> >
> > >> App-id: 2dumo-hr
> >
> > > On Tuesday, March 13, 2012 10:36:38 AM UTC+2, Richard Watson wrote:
> >
> > >> In case you're keeping track of issues thinking it's generally
> cleared up:
> >
> > >> I'm on HR and have noticed higher latencies (couple seconds instead of
> > >> e.g. 300ms) lately and sometimes higher error rates (a few instead of
> 0-3).
> > >> Yesterday over about 6 hours I got a ton of 60-second requests that
> threw
> > >> 500's with accompanying messages [1], usually on memcache sets
> hitting a
> > >> deadline exceeded.  Also, over the last couple weeks I've been
> running 3
> > >> instances permanently despite sometimes shutting them down manually.
> > >>  Usually I get by on one just fine with bursts of 2 or 3.  I've
> noticed
> > >> that one instance serves the majority of traffic with the other two
> serving
> > >> maybe 50 requests over many hours, so the shutdown isn't aggressive
> enough.
> >
> > >> "This request caused a new process to be started for your
> application..."
> > >> +
> > >> "A problem was encountered with the process that handled this request,
> > >> causing it to exit" in the same request.
> >
> > >> App-id: 2dumo-hr
> >
> > >  --
> > > 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/-/YUHiXXkGPAgJ.
> >
> > > To post to this group, send email to google-appengine@googlegroups.com
> .
> > > To unsubscribe from this group, send email to
> > > google-appengine+unsubscr...@googlegroups.com.
> > > For more options, visit this group at
> > >http://groups.google.com/group/google-appengine?hl=en.
> >
> > --
> > Johan Euphrosine (proppy)
> > Developer Programs Engineer
> > Google Developer Relations
>
> --
> You received this message because you are subscribed to the Google Groups
> "Google App Engine" group.
> To post to this group, send email to google-appengine@googlegroups.com.
> To unsubscribe from this group, send email to
> google-appengine+unsubscr...@googlegroups.com.
> For more options, visit this group at
> http://groups.google.com/group/google-appengine?hl=en.
>
>


-- 
Johan Euphrosine (proppy)
Developer Programs Engineer
Google Developer Relations

-- 
You received this message because you are subscribed to the Google Groups 
"Google App Engine" group.
To post to this group, send email to google-appengine@googlegroups.com.
To unsubscribe from this group, send email to 
google-appengine+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/google-appengine?hl=en.

Re: [google-appengine] Re: Outages?

[Johan Euphrosine]

What is your application id?

Feel free to open a production issue, if you want to investigate this
offthread:
http://code.google.com/p/googleappengine/issues/entry?template=Production%20issue


On Tue, Mar 13, 2012 at 11:44 AM, Mos  wrote:

> Same thing the last minutes on our app (HRD, Java, Low-Traffic, one
> instance, no new deployment, simple page just hitting MemCache):
>
> "Request was aborted after waiting too long to attempt to service your
> request."   -->  User sees 500er
>
> GAE-Team, what is going on the last days?  In my opinion the Google App
> Engine is unreliable and looks more like a alpha- or beta-
> cloudenvrionment
>
> Please Google share you analysis with us.
>
> Cheers
> Mos
>
>
>
>
>
> 2012/3/13 Sébastien Tromp 
>
>> Hello,
>>
>> Same thing here, since around an hour ago:
>> AppID: fiveorbsgame & fiveorbsgame-test
>>
>>
>> On Tue, Mar 13, 2012 at 9:59 AM, Miroslav Genov  wrote:
>>
>>> I'm encountering the same issue with HR app. The spike got started in
>>> about ~1 hour from now.
>>>
>>> AppID: cmsevobg
>>> Datastore: HR
>>>
>>> On Tuesday, March 13, 2012 10:36:38 AM UTC+2, Richard Watson wrote:

 In case you're keeping track of issues thinking it's generally cleared
 up:

 I'm on HR and have noticed higher latencies (couple seconds instead of
 e.g. 300ms) lately and sometimes higher error rates (a few instead of 0-3).
 Yesterday over about 6 hours I got a ton of 60-second requests that threw
 500's with accompanying messages [1], usually on memcache sets hitting a
 deadline exceeded.  Also, over the last couple weeks I've been running 3
 instances permanently despite sometimes shutting them down manually.
  Usually I get by on one just fine with bursts of 2 or 3.  I've noticed
 that one instance serves the majority of traffic with the other two serving
 maybe 50 requests over many hours, so the shutdown isn't aggressive enough.

 "This request caused a new process to be started for your
 application..."
 +
 "A problem was encountered with the process that handled this request,
 causing it to exit" in the same request.

 App-id: 2dumo-hr

>>>
>>> On Tuesday, March 13, 2012 10:36:38 AM UTC+2, Richard Watson wrote:

 In case you're keeping track of issues thinking it's generally cleared
 up:

 I'm on HR and have noticed higher latencies (couple seconds instead of
 e.g. 300ms) lately and sometimes higher error rates (a few instead of 0-3).
 Yesterday over about 6 hours I got a ton of 60-second requests that threw
 500's with accompanying messages [1], usually on memcache sets hitting a
 deadline exceeded.  Also, over the last couple weeks I've been running 3
 instances permanently despite sometimes shutting them down manually.
  Usually I get by on one just fine with bursts of 2 or 3.  I've noticed
 that one instance serves the majority of traffic with the other two serving
 maybe 50 requests over many hours, so the shutdown isn't aggressive enough.

 "This request caused a new process to be started for your
 application..."
 +
 "A problem was encountered with the process that handled this request,
 causing it to exit" in the same request.

 App-id: 2dumo-hr

>>>  --
>>> 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/-/YUHiXXkGPAgJ.
>>>
>>> To post to this group, send email to google-appengine@googlegroups.com.
>>> To unsubscribe from this group, send email to
>>> google-appengine+unsubscr...@googlegroups.com.
>>> For more options, visit this group at
>>> http://groups.google.com/group/google-appengine?hl=en.
>>>
>>
>>  --
>> You received this message because you are subscribed to the Google Groups
>> "Google App Engine" group.
>> To post to this group, send email to google-appengine@googlegroups.com.
>> To unsubscribe from this group, send email to
>> google-appengine+unsubscr...@googlegroups.com.
>> For more options, visit this group at
>> http://groups.google.com/group/google-appengine?hl=en.
>>
>
>  --
> You received this message because you are subscribed to the Google Groups
> "Google App Engine" group.
> To post to this group, send email to google-appengine@googlegroups.com.
> To unsubscribe from this group, send email to
> google-appengine+unsubscr...@googlegroups.com.
> For more options, visit this group at
> http://groups.google.com/group/google-appengine?hl=en.
>



-- 
Johan Euphrosine (proppy)
Developer Programs Engineer
Google Developer Relations

-- 
You received this message because you are subscribed to the Google Groups 
"Google App Engine" group.
To post to this group, send email to google-appengine@googlegroups.com.
To unsubscribe from this group, send email to 
google-appengine+unsubscr...@googlegroups.com.
For more options, visit th

[google-appengine] Re: Outages?

[Jason]

I'm using HRD and am still getting tons of 500s since early this
morning.

On Mar 13, 8:52 am, Johan Euphrosine  wrote:
> I believe this was related 
> to:http://code.google.com/p/googleappengine/issues/detail?id=7130
>
> This should now be fixed.
>
>
>
>
>
>
>
>
>
> On Tue, Mar 13, 2012 at 9:59 AM, Miroslav Genov  wrote:
> > I'm encountering the same issue with HR app. The spike got started in
> > about ~1 hour from now.
>
> > AppID: cmsevobg
> > Datastore: HR
>
> > On Tuesday, March 13, 2012 10:36:38 AM UTC+2, Richard Watson wrote:
>
> >> In case you're keeping track of issues thinking it's generally cleared up:
>
> >> I'm on HR and have noticed higher latencies (couple seconds instead of
> >> e.g. 300ms) lately and sometimes higher error rates (a few instead of 0-3).
> >> Yesterday over about 6 hours I got a ton of 60-second requests that threw
> >> 500's with accompanying messages [1], usually on memcache sets hitting a
> >> deadline exceeded.  Also, over the last couple weeks I've been running 3
> >> instances permanently despite sometimes shutting them down manually.
> >>  Usually I get by on one just fine with bursts of 2 or 3.  I've noticed
> >> that one instance serves the majority of traffic with the other two serving
> >> maybe 50 requests over many hours, so the shutdown isn't aggressive enough.
>
> >> "This request caused a new process to be started for your application..."
> >> +
> >> "A problem was encountered with the process that handled this request,
> >> causing it to exit" in the same request.
>
> >> App-id: 2dumo-hr
>
> > On Tuesday, March 13, 2012 10:36:38 AM UTC+2, Richard Watson wrote:
>
> >> In case you're keeping track of issues thinking it's generally cleared up:
>
> >> I'm on HR and have noticed higher latencies (couple seconds instead of
> >> e.g. 300ms) lately and sometimes higher error rates (a few instead of 0-3).
> >> Yesterday over about 6 hours I got a ton of 60-second requests that threw
> >> 500's with accompanying messages [1], usually on memcache sets hitting a
> >> deadline exceeded.  Also, over the last couple weeks I've been running 3
> >> instances permanently despite sometimes shutting them down manually.
> >>  Usually I get by on one just fine with bursts of 2 or 3.  I've noticed
> >> that one instance serves the majority of traffic with the other two serving
> >> maybe 50 requests over many hours, so the shutdown isn't aggressive enough.
>
> >> "This request caused a new process to be started for your application..."
> >> +
> >> "A problem was encountered with the process that handled this request,
> >> causing it to exit" in the same request.
>
> >> App-id: 2dumo-hr
>
> >  --
> > 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/-/YUHiXXkGPAgJ.
>
> > To post to this group, send email to google-appengine@googlegroups.com.
> > To unsubscribe from this group, send email to
> > google-appengine+unsubscr...@googlegroups.com.
> > For more options, visit this group at
> >http://groups.google.com/group/google-appengine?hl=en.
>
> --
> Johan Euphrosine (proppy)
> Developer Programs Engineer
> Google Developer Relations

-- 
You received this message because you are subscribed to the Google Groups 
"Google App Engine" group.
To post to this group, send email to google-appengine@googlegroups.com.
To unsubscribe from this group, send email to 
google-appengine+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/google-appengine?hl=en.

Re: [google-appengine] Re: Outages?

[Johan Euphrosine]

If you are not using the datastore it should be trivial to move your
application to the new HRD infrastructure.

If you don't need the same appid, just create a new HRD application and
deploy your code on it.

If you need the same appid, use the self migration tool:
https://appengine.google.com/migrating?app_id=

Feel free to open a production ticket if you need any assistance migrating
your application:
http://code.google.com/p/googleappengine/issues/entry?template=Production%20issue


On Tue, Mar 13, 2012 at 12:44 PM, charisl  wrote:

> Hello Ikai
>
> our app is *betscoreslive*. In our settings master/slave replication is
> activated but we are NOT using the datastore at all and we have been
> experiencing the DeadlineExceedExceptions and increased instance number
> mentioned by the rest of the people in the discussion. Our app is only
> using memcache.
>
> Normal operation
> during traffic peaks: instances ~25, ~45 requests/second and QPS > 1
>
> Now we observe: 12 instances doing nth with ~2 requests/second and QPS 0.2
> We had the Deadline exceptions since one week now with small periods of
> normal operation. During the problematic periods, our app is pretty
> unresponsive.
>
> Will the announced maintenance for master/slave apps will solve the issue
> for our app as well?
>
> thanks in advance
>
> Charis
>
> On Friday, March 9, 2012 9:15:35 PM UTC+2, Ikai Lan wrote:
>>
>> Hey everyone,
>>
>> Here are a few things that will help:
>>
>> 1. Application IDs (<--- if you have nothing else, at least provide this)
>> 2. What is your QPS?
>> 3. What % of your requests are errors?
>>
>> --
>> Ikai Lan
>> Developer Programs Engineer, Google App Engine
>> plus.ikailan.com
>>
>>
>>
>> On Fri, Mar 9, 2012 at 7:24 AM, Ronoaldo José de Lana Pereira <
>> rpere...@beneficiofacil.com.**br > wrote:
>>
>>> +1 for seeing the same problems on my app.
>>>
>>> It started to be worse after maintenance on March 7.
>>>
>>> Em sexta-feira, 9 de março de 2012 08h33min36s UTC-3, Nikolai escreveu:
>>>
 +1
 we had to move to our backup systems. Everything is full of 500 errors
 or hardcore latency.
 Most of the 500 errors we see aren't even logged so this seems to be a
 goole problem one abstraction layer above the app.

 And yes - sometimes we have got the same feeling, that we are the only
 ones that use appengine in a production setting. You are not alone ;)

 regards,
 nikolai

 Am Dienstag, 6. März 2012 22:17:37 UTC+1 schrieb Adam Sherman:
>
> Am I the only one seeing short duration outages? They are being
> reflected at:
>
> http://code.google.com/status/appengine
>
> But I don't see anyone else complaining anywhere, so it makes me
> worried.
>
> A.
>
>  --
>>> 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/-/**yixu1yAlMs4J
>>> .
>>>
>>> To post to this group, send email to 
>>> google-appengine@googlegroups.**com
>>> .
>>> To unsubscribe from this group, send email to
>>> google-appengine+unsubscribe@**googlegroups.com
>>> .
>>> For more options, visit this group at http://groups.google.com/**
>>> group/google-appengine?hl=en
>>> .
>>>
>>
>>  --
> 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/-/W1KVvW7v-SEJ.
>
> To post to this group, send email to google-appengine@googlegroups.com.
> To unsubscribe from this group, send email to
> google-appengine+unsubscr...@googlegroups.com.
> For more options, visit this group at
> http://groups.google.com/group/google-appengine?hl=en.
>



-- 
Johan Euphrosine (proppy)
Developer Programs Engineer
Google Developer Relations

-- 
You received this message because you are subscribed to the Google Groups 
"Google App Engine" group.
To post to this group, send email to google-appengine@googlegroups.com.
To unsubscribe from this group, send email to 
google-appengine+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/google-appengine?hl=en.

Re: [google-appengine] Re: Outages?

[Johan Euphrosine]

As Chris pointed earlier in that thread, M/S app are more vulnerable to
this kind of transient infrastructure issues because moving them around
require a maintenance period.

HRD applications are covered by the SLA, replicated around multiple
datacenter, and better distributed if we notice an issue impacting one or
many of them we can easily take actions without impacting other
applications.

I strongly suggest to you to try out the self migration tool in your
administration console, depending of the size of your data and your write
QPS, the read only period needed to migrate your application could be very
small:
https://appengine.google.com/migrating?app_id=

On Tue, Mar 13, 2012 at 2:37 PM, Ronoaldo José de Lana Pereira <
rpere...@beneficiofacil.com.br> wrote:

> This is very disturbing ... Our M/S app is getting higher error rates and
> some instances take from 15s to 70s to start. We can't do anything about
> this and even debug what is happening. If there was a issue with our code,
> they should always take 70s to start! I really can't understand or think
> about what in our code we are loading the whole world to take all that
> time... Then the solutions is: move to HRD and ... experience the same load
> time on app startup??? So, what can I do!!!
>
> Sorry to the rude speaking but I'm very concerned. We started the process
> to get operational support and plan our migration to have the SLA, but if
> our app startup will continue taking a lot of time I really can imagine
> what to do...
>
> Googlers, does the startup problem is getting solved for both M/S and HRD?
> Only HRD? None? Is there any thing we can do to avoid that strange behavior
> of our instances? Instance startup seems to be vital to the application's
> health: if your app takes to much time to startup then all concurrent
> requests to that instances die with 500's. This is very odd, and the
> "warmup" requests seems to never work. By our observations and other people
> observations, even if you set a fixed min_idle instances to be always
> there, they don't serve the traffic and you still get errors!
>
> Hope to see some answers, we really liked GAE in our first year woking
> with the platform, and now I feel completely lost...
>
> Best Regards,
>
> -Ronoaldo
>
> Em terça-feira, 13 de março de 2012 07h51min03s UTC-3, Richard Watson
> escreveu:
>
>> My graph showing ms/sec (attached) over last 24h.  Average spikes were up
>> to 32 seconds, but I think all the errors were 60+-1 sec.
>>
>> On Tuesday, March 13, 2012 10:36:38 AM UTC+2, Richard Watson wrote:
>>>
>>> In case you're keeping track of issues thinking it's generally cleared
>>> up:
>>>
>>> I'm on HR and have noticed higher latencies (couple seconds instead of
>>> e.g. 300ms) lately and sometimes higher error rates (a few instead of 0-3).
>>> Yesterday over about 6 hours I got a ton of 60-second requests that threw
>>> 500's with accompanying messages [1], usually on memcache sets hitting a
>>> deadline exceeded.  Also, over the last couple weeks I've been running 3
>>> instances permanently despite sometimes shutting them down manually.
>>>  Usually I get by on one just fine with bursts of 2 or 3.  I've noticed
>>> that one instance serves the majority of traffic with the other two serving
>>> maybe 50 requests over many hours, so the shutdown isn't aggressive enough.
>>>
>>> "This request caused a new process to be started for your application..."
>>> +
>>> "A problem was encountered with the process that handled this request,
>>> causing it to exit" in the same request.
>>>
>>> App-id: 2dumo-hr
>>>
>>  --
> 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/-/6r3NpHShJcgJ.
>
> To post to this group, send email to google-appengine@googlegroups.com.
> To unsubscribe from this group, send email to
> google-appengine+unsubscr...@googlegroups.com.
> For more options, visit this group at
> http://groups.google.com/group/google-appengine?hl=en.
>



-- 
Johan Euphrosine (proppy)
Developer Programs Engineer
Google Developer Relations

-- 
You received this message because you are subscribed to the Google Groups 
"Google App Engine" group.
To post to this group, send email to google-appengine@googlegroups.com.
To unsubscribe from this group, send email to 
google-appengine+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/google-appengine?hl=en.

Re: [google-appengine] Re: Outages?

[Johan Euphrosine]

Hi,

I believe this was also related to:
http://code.google.com/p/googleappengine/issues/detail?id=7130

And should now be fixed.

On Tue, Mar 13, 2012 at 10:02 AM, Sébastien Tromp  wrote:

> Hello,
>
> Same thing here, since around an hour ago:
> AppID: fiveorbsgame & fiveorbsgame-test
>
>
> On Tue, Mar 13, 2012 at 9:59 AM, Miroslav Genov  wrote:
>
>> I'm encountering the same issue with HR app. The spike got started in
>> about ~1 hour from now.
>>
>> AppID: cmsevobg
>> Datastore: HR
>>
>> On Tuesday, March 13, 2012 10:36:38 AM UTC+2, Richard Watson wrote:
>>>
>>> In case you're keeping track of issues thinking it's generally cleared
>>> up:
>>>
>>> I'm on HR and have noticed higher latencies (couple seconds instead of
>>> e.g. 300ms) lately and sometimes higher error rates (a few instead of 0-3).
>>> Yesterday over about 6 hours I got a ton of 60-second requests that threw
>>> 500's with accompanying messages [1], usually on memcache sets hitting a
>>> deadline exceeded.  Also, over the last couple weeks I've been running 3
>>> instances permanently despite sometimes shutting them down manually.
>>>  Usually I get by on one just fine with bursts of 2 or 3.  I've noticed
>>> that one instance serves the majority of traffic with the other two serving
>>> maybe 50 requests over many hours, so the shutdown isn't aggressive enough.
>>>
>>> "This request caused a new process to be started for your application..."
>>> +
>>> "A problem was encountered with the process that handled this request,
>>> causing it to exit" in the same request.
>>>
>>> App-id: 2dumo-hr
>>>
>>
>> On Tuesday, March 13, 2012 10:36:38 AM UTC+2, Richard Watson wrote:
>>>
>>> In case you're keeping track of issues thinking it's generally cleared
>>> up:
>>>
>>> I'm on HR and have noticed higher latencies (couple seconds instead of
>>> e.g. 300ms) lately and sometimes higher error rates (a few instead of 0-3).
>>> Yesterday over about 6 hours I got a ton of 60-second requests that threw
>>> 500's with accompanying messages [1], usually on memcache sets hitting a
>>> deadline exceeded.  Also, over the last couple weeks I've been running 3
>>> instances permanently despite sometimes shutting them down manually.
>>>  Usually I get by on one just fine with bursts of 2 or 3.  I've noticed
>>> that one instance serves the majority of traffic with the other two serving
>>> maybe 50 requests over many hours, so the shutdown isn't aggressive enough.
>>>
>>> "This request caused a new process to be started for your application..."
>>> +
>>> "A problem was encountered with the process that handled this request,
>>> causing it to exit" in the same request.
>>>
>>> App-id: 2dumo-hr
>>>
>>  --
>> 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/-/YUHiXXkGPAgJ.
>>
>> To post to this group, send email to google-appengine@googlegroups.com.
>> To unsubscribe from this group, send email to
>> google-appengine+unsubscr...@googlegroups.com.
>> For more options, visit this group at
>> http://groups.google.com/group/google-appengine?hl=en.
>>
>
>  --
> You received this message because you are subscribed to the Google Groups
> "Google App Engine" group.
> To post to this group, send email to google-appengine@googlegroups.com.
> To unsubscribe from this group, send email to
> google-appengine+unsubscr...@googlegroups.com.
> For more options, visit this group at
> http://groups.google.com/group/google-appengine?hl=en.
>



-- 
Johan Euphrosine (proppy)
Developer Programs Engineer
Google Developer Relations

-- 
You received this message because you are subscribed to the Google Groups 
"Google App Engine" group.
To post to this group, send email to google-appengine@googlegroups.com.
To unsubscribe from this group, send email to 
google-appengine+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/google-appengine?hl=en.

Re: [google-appengine] Re: Outages?

[Johan Euphrosine]

I believe this was related to:
http://code.google.com/p/googleappengine/issues/detail?id=7130

This should now be fixed.

On Tue, Mar 13, 2012 at 9:59 AM, Miroslav Genov  wrote:

> I'm encountering the same issue with HR app. The spike got started in
> about ~1 hour from now.
>
> AppID: cmsevobg
> Datastore: HR
>
> On Tuesday, March 13, 2012 10:36:38 AM UTC+2, Richard Watson wrote:
>>
>> In case you're keeping track of issues thinking it's generally cleared up:
>>
>> I'm on HR and have noticed higher latencies (couple seconds instead of
>> e.g. 300ms) lately and sometimes higher error rates (a few instead of 0-3).
>> Yesterday over about 6 hours I got a ton of 60-second requests that threw
>> 500's with accompanying messages [1], usually on memcache sets hitting a
>> deadline exceeded.  Also, over the last couple weeks I've been running 3
>> instances permanently despite sometimes shutting them down manually.
>>  Usually I get by on one just fine with bursts of 2 or 3.  I've noticed
>> that one instance serves the majority of traffic with the other two serving
>> maybe 50 requests over many hours, so the shutdown isn't aggressive enough.
>>
>> "This request caused a new process to be started for your application..."
>> +
>> "A problem was encountered with the process that handled this request,
>> causing it to exit" in the same request.
>>
>> App-id: 2dumo-hr
>>
>
> On Tuesday, March 13, 2012 10:36:38 AM UTC+2, Richard Watson wrote:
>>
>> In case you're keeping track of issues thinking it's generally cleared up:
>>
>> I'm on HR and have noticed higher latencies (couple seconds instead of
>> e.g. 300ms) lately and sometimes higher error rates (a few instead of 0-3).
>> Yesterday over about 6 hours I got a ton of 60-second requests that threw
>> 500's with accompanying messages [1], usually on memcache sets hitting a
>> deadline exceeded.  Also, over the last couple weeks I've been running 3
>> instances permanently despite sometimes shutting them down manually.
>>  Usually I get by on one just fine with bursts of 2 or 3.  I've noticed
>> that one instance serves the majority of traffic with the other two serving
>> maybe 50 requests over many hours, so the shutdown isn't aggressive enough.
>>
>> "This request caused a new process to be started for your application..."
>> +
>> "A problem was encountered with the process that handled this request,
>> causing it to exit" in the same request.
>>
>> App-id: 2dumo-hr
>>
>  --
> 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/-/YUHiXXkGPAgJ.
>
> To post to this group, send email to google-appengine@googlegroups.com.
> To unsubscribe from this group, send email to
> google-appengine+unsubscr...@googlegroups.com.
> For more options, visit this group at
> http://groups.google.com/group/google-appengine?hl=en.
>



-- 
Johan Euphrosine (proppy)
Developer Programs Engineer
Google Developer Relations

-- 
You received this message because you are subscribed to the Google Groups 
"Google App Engine" group.
To post to this group, send email to google-appengine@googlegroups.com.
To unsubscribe from this group, send email to 
google-appengine+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/google-appengine?hl=en.

Re: [google-appengine] Re: Outages?

[Ronoaldo José de Lana Pereira]

This is very disturbing ... Our M/S app is getting higher error rates and 
some instances take from 15s to 70s to start. We can't do anything about 
this and even debug what is happening. If there was a issue with our code, 
they should always take 70s to start! I really can't understand or think 
about what in our code we are loading the whole world to take all that 
time... Then the solutions is: move to HRD and ... experience the same load 
time on app startup??? So, what can I do!!!

Sorry to the rude speaking but I'm very concerned. We started the process 
to get operational support and plan our migration to have the SLA, but if 
our app startup will continue taking a lot of time I really can imagine 
what to do...

Googlers, does the startup problem is getting solved for both M/S and HRD? 
Only HRD? None? Is there any thing we can do to avoid that strange behavior 
of our instances? Instance startup seems to be vital to the application's 
health: if your app takes to much time to startup then all concurrent 
requests to that instances die with 500's. This is very odd, and the 
"warmup" requests seems to never work. By our observations and other people 
observations, even if you set a fixed min_idle instances to be always 
there, they don't serve the traffic and you still get errors!

Hope to see some answers, we really liked GAE in our first year woking with 
the platform, and now I feel completely lost...

Best Regards,

-Ronoaldo

Em terça-feira, 13 de março de 2012 07h51min03s UTC-3, Richard Watson 
escreveu:
>
> My graph showing ms/sec (attached) over last 24h.  Average spikes were up 
> to 32 seconds, but I think all the errors were 60+-1 sec.
>
> On Tuesday, March 13, 2012 10:36:38 AM UTC+2, Richard Watson wrote:
>>
>> In case you're keeping track of issues thinking it's generally cleared up:
>>
>> I'm on HR and have noticed higher latencies (couple seconds instead of 
>> e.g. 300ms) lately and sometimes higher error rates (a few instead of 0-3). 
>> Yesterday over about 6 hours I got a ton of 60-second requests that threw 
>> 500's with accompanying messages [1], usually on memcache sets hitting a 
>> deadline exceeded.  Also, over the last couple weeks I've been running 3 
>> instances permanently despite sometimes shutting them down manually. 
>>  Usually I get by on one just fine with bursts of 2 or 3.  I've noticed 
>> that one instance serves the majority of traffic with the other two serving 
>> maybe 50 requests over many hours, so the shutdown isn't aggressive enough.
>>
>> "This request caused a new process to be started for your application..."
>> +
>> "A problem was encountered with the process that handled this request, 
>> causing it to exit" in the same request.
>>
>> App-id: 2dumo-hr
>>
>

-- 
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/-/6r3NpHShJcgJ.
To post to this group, send email to google-appengine@googlegroups.com.
To unsubscribe from this group, send email to 
google-appengine+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/google-appengine?hl=en.

Re: [google-appengine] cannot delete old version of my application

[emerix]

Hello,

How can I get this limit of 100 versions per application?
My old and new applications are still limited to 10 versions.

Thank you
Maxime

On Monday, June 14, 2010 9:02:48 PM UTC+2, Ikai L (Google) wrote:
>
> Are you uploading versions or new applications? You should have a limit of 
> 100 versions, not 10.
>
> On Sun, Jun 13, 2010 at 4:22 AM, Ohad R  wrote:
>
>> hi there
>> i upload several versions of my app to GAE. after i get to 10
>> versions, i was notified that i must delete old versions. but some
>> versions cannot be deleted from some unknown reason. when i try to
>> delete it , i get an error:
>> Server Error
>> A server error has occurred.
>> Return to Applications screen »
>>
>> anyone has an idea?
>> (my app name is blpatch...@appspot.com)
>>
>> thanks a lot,
>> Ohad
>>
>> --
>> You received this message because you are subscribed to the Google Groups 
>> "Google App Engine" group.
>> To post to this group, send email to google-appengine@googlegroups.com.
>> To unsubscribe from this group, send email to 
>> google-appengine+unsubscr...@googlegroups.com.
>> For more options, visit this group at 
>> http://groups.google.com/group/google-appengine?hl=en.
>>
>>
>
>
> -- 
> Ikai Lan 
> Developer Programs Engineer, Google App Engine
> Blog: http://googleappengine.blogspot.com 
> Twitter: http://twitter.com/app_engine
> Reddit: http://www.reddit.com/r/appengine
>
>
On Monday, June 14, 2010 9:02:48 PM UTC+2, Ikai L (Google) wrote:
>
> Are you uploading versions or new applications? You should have a limit of 
> 100 versions, not 10.
>
> On Sun, Jun 13, 2010 at 4:22 AM, Ohad R  wrote:
>
>> hi there
>> i upload several versions of my app to GAE. after i get to 10
>> versions, i was notified that i must delete old versions. but some
>> versions cannot be deleted from some unknown reason. when i try to
>> delete it , i get an error:
>> Server Error
>> A server error has occurred.
>> Return to Applications screen »
>>
>> anyone has an idea?
>> (my app name is blpatch...@appspot.com)
>>
>> thanks a lot,
>> Ohad
>>
>> --
>> You received this message because you are subscribed to the Google Groups 
>> "Google App Engine" group.
>> To post to this group, send email to google-appengine@googlegroups.com.
>> To unsubscribe from this group, send email to 
>> google-appengine+unsubscr...@googlegroups.com.
>> For more options, visit this group at 
>> http://groups.google.com/group/google-appengine?hl=en.
>>
>>
>
>
> -- 
> Ikai Lan 
> Developer Programs Engineer, Google App Engine
> Blog: http://googleappengine.blogspot.com 
> Twitter: http://twitter.com/app_engine
> Reddit: http://www.reddit.com/r/appengine
>
>

-- 
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/-/3zbwUuEDRkkJ.
To post to this group, send email to google-appengine@googlegroups.com.
To unsubscribe from this group, send email to 
google-appengine+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/google-appengine?hl=en.

Re: [google-appengine] Re: Outages?

[charisl]

Hello Ikai

our app is *betscoreslive*. In our settings master/slave replication is 
activated but we are NOT using the datastore at all and we have been 
experiencing the DeadlineExceedExceptions and increased instance number 
mentioned by the rest of the people in the discussion. Our app is only 
using memcache.

Normal operation
during traffic peaks: instances ~25, ~45 requests/second and QPS > 1

Now we observe: 12 instances doing nth with ~2 requests/second and QPS 0.2
We had the Deadline exceptions since one week now with small periods of 
normal operation. During the problematic periods, our app is pretty 
unresponsive.

Will the announced maintenance for master/slave apps will solve the issue 
for our app as well?

thanks in advance

Charis

On Friday, March 9, 2012 9:15:35 PM UTC+2, Ikai Lan wrote:
>
> Hey everyone,
>
> Here are a few things that will help:
>
> 1. Application IDs (<--- if you have nothing else, at least provide this)
> 2. What is your QPS?
> 3. What % of your requests are errors?
>
> --
> Ikai Lan 
> Developer Programs Engineer, Google App Engine
> plus.ikailan.com
>
>
>
> On Fri, Mar 9, 2012 at 7:24 AM, Ronoaldo José de Lana Pereira <
> rpere...@beneficiofacil.com.br> wrote:
>
>> +1 for seeing the same problems on my app.
>>
>> It started to be worse after maintenance on March 7.
>>
>> Em sexta-feira, 9 de março de 2012 08h33min36s UTC-3, Nikolai escreveu:
>>
>>> +1
>>> we had to move to our backup systems. Everything is full of 500 errors 
>>> or hardcore latency.
>>> Most of the 500 errors we see aren't even logged so this seems to be a 
>>> goole problem one abstraction layer above the app.
>>>
>>> And yes - sometimes we have got the same feeling, that we are the only 
>>> ones that use appengine in a production setting. You are not alone ;)
>>>
>>> regards,
>>> nikolai
>>>
>>> Am Dienstag, 6. März 2012 22:17:37 UTC+1 schrieb Adam Sherman:

 Am I the only one seeing short duration outages? They are being 
 reflected at:

 http://code.google.com/status/**appengine

 But I don't see anyone else complaining anywhere, so it makes me 
 worried.

 A.

  -- 
>> 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/-/yixu1yAlMs4J.
>>
>> To post to this group, send email to google-appengine@googlegroups.com.
>> To unsubscribe from this group, send email to 
>> google-appengine+unsubscr...@googlegroups.com.
>> For more options, visit this group at 
>> http://groups.google.com/group/google-appengine?hl=en.
>>
>
>

-- 
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/-/W1KVvW7v-SEJ.
To post to this group, send email to google-appengine@googlegroups.com.
To unsubscribe from this group, send email to 
google-appengine+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/google-appengine?hl=en.

Re: [google-appengine] Re: Outages?

[Richard Watson]

My graph showing ms/sec (attached) over last 24h.  Average spikes were up 
to 32 seconds, but I think all the errors were 60+-1 sec.

On Tuesday, March 13, 2012 10:36:38 AM UTC+2, Richard Watson wrote:
>
> In case you're keeping track of issues thinking it's generally cleared up:
>
> I'm on HR and have noticed higher latencies (couple seconds instead of 
> e.g. 300ms) lately and sometimes higher error rates (a few instead of 0-3). 
> Yesterday over about 6 hours I got a ton of 60-second requests that threw 
> 500's with accompanying messages [1], usually on memcache sets hitting a 
> deadline exceeded.  Also, over the last couple weeks I've been running 3 
> instances permanently despite sometimes shutting them down manually. 
>  Usually I get by on one just fine with bursts of 2 or 3.  I've noticed 
> that one instance serves the majority of traffic with the other two serving 
> maybe 50 requests over many hours, so the shutdown isn't aggressive enough.
>
> "This request caused a new process to be started for your application..."
> +
> "A problem was encountered with the process that handled this request, 
> causing it to exit" in the same request.
>
> App-id: 2dumo-hr
>

-- 
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/-/7CPSW2zXP5QJ.
To post to this group, send email to google-appengine@googlegroups.com.
To unsubscribe from this group, send email to 
google-appengine+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/google-appengine?hl=en.

<>

Re: [google-appengine] Re: Outages?

[Mos]

Same thing the last minutes on our app (HRD, Java, Low-Traffic, one
instance, no new deployment, simple page just hitting MemCache):

"Request was aborted after waiting too long to attempt to service your
request."   -->  User sees 500er

GAE-Team, what is going on the last days?  In my opinion the Google App
Engine is unreliable and looks more like a alpha- or beta-
cloudenvrionment

Please Google share you analysis with us.

Cheers
Mos




2012/3/13 Sébastien Tromp 

> Hello,
>
> Same thing here, since around an hour ago:
> AppID: fiveorbsgame & fiveorbsgame-test
>
>
> On Tue, Mar 13, 2012 at 9:59 AM, Miroslav Genov  wrote:
>
>> I'm encountering the same issue with HR app. The spike got started in
>> about ~1 hour from now.
>>
>> AppID: cmsevobg
>> Datastore: HR
>>
>> On Tuesday, March 13, 2012 10:36:38 AM UTC+2, Richard Watson wrote:
>>>
>>> In case you're keeping track of issues thinking it's generally cleared
>>> up:
>>>
>>> I'm on HR and have noticed higher latencies (couple seconds instead of
>>> e.g. 300ms) lately and sometimes higher error rates (a few instead of 0-3).
>>> Yesterday over about 6 hours I got a ton of 60-second requests that threw
>>> 500's with accompanying messages [1], usually on memcache sets hitting a
>>> deadline exceeded.  Also, over the last couple weeks I've been running 3
>>> instances permanently despite sometimes shutting them down manually.
>>>  Usually I get by on one just fine with bursts of 2 or 3.  I've noticed
>>> that one instance serves the majority of traffic with the other two serving
>>> maybe 50 requests over many hours, so the shutdown isn't aggressive enough.
>>>
>>> "This request caused a new process to be started for your application..."
>>> +
>>> "A problem was encountered with the process that handled this request,
>>> causing it to exit" in the same request.
>>>
>>> App-id: 2dumo-hr
>>>
>>
>> On Tuesday, March 13, 2012 10:36:38 AM UTC+2, Richard Watson wrote:
>>>
>>> In case you're keeping track of issues thinking it's generally cleared
>>> up:
>>>
>>> I'm on HR and have noticed higher latencies (couple seconds instead of
>>> e.g. 300ms) lately and sometimes higher error rates (a few instead of 0-3).
>>> Yesterday over about 6 hours I got a ton of 60-second requests that threw
>>> 500's with accompanying messages [1], usually on memcache sets hitting a
>>> deadline exceeded.  Also, over the last couple weeks I've been running 3
>>> instances permanently despite sometimes shutting them down manually.
>>>  Usually I get by on one just fine with bursts of 2 or 3.  I've noticed
>>> that one instance serves the majority of traffic with the other two serving
>>> maybe 50 requests over many hours, so the shutdown isn't aggressive enough.
>>>
>>> "This request caused a new process to be started for your application..."
>>> +
>>> "A problem was encountered with the process that handled this request,
>>> causing it to exit" in the same request.
>>>
>>> App-id: 2dumo-hr
>>>
>>  --
>> 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/-/YUHiXXkGPAgJ.
>>
>> To post to this group, send email to google-appengine@googlegroups.com.
>> To unsubscribe from this group, send email to
>> google-appengine+unsubscr...@googlegroups.com.
>> For more options, visit this group at
>> http://groups.google.com/group/google-appengine?hl=en.
>>
>
>  --
> You received this message because you are subscribed to the Google Groups
> "Google App Engine" group.
> To post to this group, send email to google-appengine@googlegroups.com.
> To unsubscribe from this group, send email to
> google-appengine+unsubscr...@googlegroups.com.
> For more options, visit this group at
> http://groups.google.com/group/google-appengine?hl=en.
>

-- 
You received this message because you are subscribed to the Google Groups 
"Google App Engine" group.
To post to this group, send email to google-appengine@googlegroups.com.
To unsubscribe from this group, send email to 
google-appengine+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/google-appengine?hl=en.

Re: [google-appengine] Re: Outages?

[Pieter Coucke]

Same here, very slow and frequent instance startups.  I use the HR
datastore.

I've set idle instances to 2 F4s but I have the impression that the
scheduler prefers to start a new instance instead of using one of the
available idle ones.


-- 
Pieter Coucke
Onthoo BVBA
zamtam.com  | cashcontact.com

-- 
You received this message because you are subscribed to the Google Groups 
"Google App Engine" group.
To post to this group, send email to google-appengine@googlegroups.com.
To unsubscribe from this group, send email to 
google-appengine+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/google-appengine?hl=en.

Re: [google-appengine] Re: Outages?

[Miroslav Genov]

Ops my mistake, our HR id is cmsevobg-hr. Normally we get initialization 
time for ~10 seconds, now the time is 38 seconds using F4 CPU model. 

Here are some exception traces that might help

   1. 
   
   Failed startup of context 
com.google.apphosting.utils.jetty.RuntimeAppEngineWebAppContext@199f8e6{/,/base/data/home/apps/s~cmsevobg-hr/production.357324755677494831}
   java.lang.NullPointerException
at 
com.google.inject.servlet.GuiceServletContextListener.contextInitialized(GuiceServletContextListener.java:46)
at 
xxx.xxx.xxx.xxx.AppBootstrap.contextInitialized(AdmBootstrap.java:189)
at 
org.mortbay.jetty.handler.ContextHandler.startContext(ContextHandler.java:548)
at org.mortbay.jetty.servlet.Context.startContext(Context.java:136)
at 
org.mortbay.jetty.webapp.WebAppContext.startContext(WebAppContext.java:1250)
at 
org.mortbay.jetty.handler.ContextHandler.doStart(ContextHandler.java:517)
at 
org.mortbay.jetty.webapp.WebAppContext.doStart(WebAppContext.java:467)
at 
org.mortbay.component.AbstractLifeCycle.start(AbstractLifeCycle.java:50)
at 
com.google.apphosting.runtime.jetty.AppVersionHandlerMap.createHandler(AppVersionHandlerMap.java:202)
at 
com.google.apphosting.runtime.jetty.AppVersionHandlerMap.getHandler(AppVersionHandlerMap.java:171)
at 
com.google.apphosting.runtime.jetty.JettyServletEngineAdapter.serviceRequest(JettyServletEngineAdapter.java:123)
at 
com.google.apphosting.runtime.JavaRuntime$RequestRunnable.run(JavaRuntime.java:422)
at 
com.google.tracing.TraceContext$TraceContextRunnable.runInContext(TraceContext.java:449)
at 
com.google.tracing.TraceContext$TraceContextRunnable$1.run(TraceContext.java:455)
at com.google.tracing.TraceContext.runInContext(TraceContext.java:695)
at 
com.google.tracing.TraceContext$AbstractTraceContextCallback.runInInheritedContextNoUnref(TraceContext.java:333)
at 
com.google.tracing.TraceContext$AbstractTraceContextCallback.runInInheritedContext(TraceContext.java:325)
at 
com.google.tracing.TraceContext$TraceContextRunnable.run(TraceContext.java:453)
at 
com.google.apphosting.runtime.ThreadGroupPool$PoolEntry.run(ThreadGroupPool.java:251)
at java.lang.Thread.run(Thread.java:679)
   
   2. C2012-03-13 11:02:31.883
   
   Uncaught exception from servlet
   javax.servlet.UnavailableException: Initialization failed.
at 
com.google.apphosting.runtime.jetty.AppVersionHandlerMap.createHandler(AppVersionHandlerMap.java:211)
at 
com.google.apphosting.runtime.jetty.AppVersionHandlerMap.getHandler(AppVersionHandlerMap.java:171)
at 
com.google.apphosting.runtime.jetty.JettyServletEngineAdapter.serviceRequest(JettyServletEngineAdapter.java:123)
at 
com.google.apphosting.runtime.JavaRuntime$RequestRunnable.run(JavaRuntime.java:422)
at 
com.google.tracing.TraceContext$TraceContextRunnable.runInContext(TraceContext.java:449)
at 
com.google.tracing.TraceContext$TraceContextRunnable$1.run(TraceContext.java:455)
at com.google.tracing.TraceContext.runInContext(TraceContext.java:695)
at 
com.google.tracing.TraceContext$AbstractTraceContextCallback.runInInheritedContextNoUnref(TraceContext.java:333)
at 
com.google.tracing.TraceContext$AbstractTraceContextCallback.runInInheritedContext(TraceContext.java:325)
at 
com.google.tracing.TraceContext$TraceContextRunnable.run(TraceContext.java:453)
at 
com.google.apphosting.runtime.ThreadGroupPool$PoolEntry.run(ThreadGroupPool.java:251)
at java.lang.Thread.run(Thread.java:679)
   
   

On Tuesday, March 13, 2012 10:59:18 AM UTC+2, Miroslav Genov wrote:
>
> I'm encountering the same issue with HR app. The spike got started in 
> about ~1 hour from now. 
>
> AppID: cmsevobg
> Datastore: HR
>
> On Tuesday, March 13, 2012 10:36:38 AM UTC+2, Richard Watson wrote:
>>
>> In case you're keeping track of issues thinking it's generally cleared up:
>>
>> I'm on HR and have noticed higher latencies (couple seconds instead of 
>> e.g. 300ms) lately and sometimes higher error rates (a few instead of 0-3). 
>> Yesterday over about 6 hours I got a ton of 60-second requests that threw 
>> 500's with accompanying messages [1], usually on memcache sets hitting a 
>> deadline exceeded.  Also, over the last couple weeks I've been running 3 
>> instances permanently despite sometimes shutting them down manually. 
>>  Usually I get by on one just fine with bursts of 2 or 3.  I've noticed 
>> that one instance serves the majority of traffic with the other two serving 
>> maybe 50 requests over many hours, so the shutdown isn't aggressive enough.
>>
>> "This request caused a new process to be started for your application..."
>> +
>> "A problem was encountered with the process that handled this request, 
>> causing it to exit" in the same request.
>>
>> App-id: 2dumo-hr
>>
>
> On Tuesday, March 13, 2012 10:36:38 

Re: [google-appengine] Re: Outages?

[Sébastien Tromp]

Hello,

Same thing here, since around an hour ago:
AppID: fiveorbsgame & fiveorbsgame-test

On Tue, Mar 13, 2012 at 9:59 AM, Miroslav Genov  wrote:

> I'm encountering the same issue with HR app. The spike got started in
> about ~1 hour from now.
>
> AppID: cmsevobg
> Datastore: HR
>
> On Tuesday, March 13, 2012 10:36:38 AM UTC+2, Richard Watson wrote:
>>
>> In case you're keeping track of issues thinking it's generally cleared up:
>>
>> I'm on HR and have noticed higher latencies (couple seconds instead of
>> e.g. 300ms) lately and sometimes higher error rates (a few instead of 0-3).
>> Yesterday over about 6 hours I got a ton of 60-second requests that threw
>> 500's with accompanying messages [1], usually on memcache sets hitting a
>> deadline exceeded.  Also, over the last couple weeks I've been running 3
>> instances permanently despite sometimes shutting them down manually.
>>  Usually I get by on one just fine with bursts of 2 or 3.  I've noticed
>> that one instance serves the majority of traffic with the other two serving
>> maybe 50 requests over many hours, so the shutdown isn't aggressive enough.
>>
>> "This request caused a new process to be started for your application..."
>> +
>> "A problem was encountered with the process that handled this request,
>> causing it to exit" in the same request.
>>
>> App-id: 2dumo-hr
>>
>
> On Tuesday, March 13, 2012 10:36:38 AM UTC+2, Richard Watson wrote:
>>
>> In case you're keeping track of issues thinking it's generally cleared up:
>>
>> I'm on HR and have noticed higher latencies (couple seconds instead of
>> e.g. 300ms) lately and sometimes higher error rates (a few instead of 0-3).
>> Yesterday over about 6 hours I got a ton of 60-second requests that threw
>> 500's with accompanying messages [1], usually on memcache sets hitting a
>> deadline exceeded.  Also, over the last couple weeks I've been running 3
>> instances permanently despite sometimes shutting them down manually.
>>  Usually I get by on one just fine with bursts of 2 or 3.  I've noticed
>> that one instance serves the majority of traffic with the other two serving
>> maybe 50 requests over many hours, so the shutdown isn't aggressive enough.
>>
>> "This request caused a new process to be started for your application..."
>> +
>> "A problem was encountered with the process that handled this request,
>> causing it to exit" in the same request.
>>
>> App-id: 2dumo-hr
>>
>  --
> 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/-/YUHiXXkGPAgJ.
>
> To post to this group, send email to google-appengine@googlegroups.com.
> To unsubscribe from this group, send email to
> google-appengine+unsubscr...@googlegroups.com.
> For more options, visit this group at
> http://groups.google.com/group/google-appengine?hl=en.
>

-- 
You received this message because you are subscribed to the Google Groups 
"Google App Engine" group.
To post to this group, send email to google-appengine@googlegroups.com.
To unsubscribe from this group, send email to 
google-appengine+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/google-appengine?hl=en.

Re: [google-appengine] Re: Outages?

[Miroslav Genov]

I'm encountering the same issue with HR app. The spike got started in about 
~1 hour from now. 

AppID: cmsevobg
Datastore: HR

On Tuesday, March 13, 2012 10:36:38 AM UTC+2, Richard Watson wrote:
>
> In case you're keeping track of issues thinking it's generally cleared up:
>
> I'm on HR and have noticed higher latencies (couple seconds instead of 
> e.g. 300ms) lately and sometimes higher error rates (a few instead of 0-3). 
> Yesterday over about 6 hours I got a ton of 60-second requests that threw 
> 500's with accompanying messages [1], usually on memcache sets hitting a 
> deadline exceeded.  Also, over the last couple weeks I've been running 3 
> instances permanently despite sometimes shutting them down manually. 
>  Usually I get by on one just fine with bursts of 2 or 3.  I've noticed 
> that one instance serves the majority of traffic with the other two serving 
> maybe 50 requests over many hours, so the shutdown isn't aggressive enough.
>
> "This request caused a new process to be started for your application..."
> +
> "A problem was encountered with the process that handled this request, 
> causing it to exit" in the same request.
>
> App-id: 2dumo-hr
>

On Tuesday, March 13, 2012 10:36:38 AM UTC+2, Richard Watson wrote:
>
> In case you're keeping track of issues thinking it's generally cleared up:
>
> I'm on HR and have noticed higher latencies (couple seconds instead of 
> e.g. 300ms) lately and sometimes higher error rates (a few instead of 0-3). 
> Yesterday over about 6 hours I got a ton of 60-second requests that threw 
> 500's with accompanying messages [1], usually on memcache sets hitting a 
> deadline exceeded.  Also, over the last couple weeks I've been running 3 
> instances permanently despite sometimes shutting them down manually. 
>  Usually I get by on one just fine with bursts of 2 or 3.  I've noticed 
> that one instance serves the majority of traffic with the other two serving 
> maybe 50 requests over many hours, so the shutdown isn't aggressive enough.
>
> "This request caused a new process to be started for your application..."
> +
> "A problem was encountered with the process that handled this request, 
> causing it to exit" in the same request.
>
> App-id: 2dumo-hr
>

-- 
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/-/YUHiXXkGPAgJ.
To post to this group, send email to google-appengine@googlegroups.com.
To unsubscribe from this group, send email to 
google-appengine+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/google-appengine?hl=en.

<>

Re: [google-appengine] Re: Outages?

[Richard Watson]

In case you're keeping track of issues thinking it's generally cleared up:

I'm on HR and have noticed higher latencies (couple seconds instead of e.g. 
300ms) lately and sometimes higher error rates (a few instead of 0-3). 
Yesterday over about 6 hours I got a ton of 60-second requests that threw 
500's with accompanying messages [1], usually on memcache sets hitting a 
deadline exceeded.  Also, over the last couple weeks I've been running 3 
instances permanently despite sometimes shutting them down manually. 
 Usually I get by on one just fine with bursts of 2 or 3.  I've noticed 
that one instance serves the majority of traffic with the other two serving 
maybe 50 requests over many hours, so the shutdown isn't aggressive enough.

"This request caused a new process to be started for your application..."
+
"A problem was encountered with the process that handled this request, 
causing it to exit" in the same request.

App-id: 2dumo-hr

-- 
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/-/Hyli1fDXHz8J.
To post to this group, send email to google-appengine@googlegroups.com.
To unsubscribe from this group, send email to 
google-appengine+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/google-appengine?hl=en.