[google-appengine] Re: GAE Java aggressively killing new instances again

Yep, Latency went pear shaped yesterday. (Slaps forehead.) David -- You received this message because you are subscribed to the Google Groups "Google App Engine" group. To unsubscribe from this group and stop receiving emails from it, send an email to google-appengine+unsubscr...@googlegroup

Re: [google-appengine] using memcache without the datastore.

Of course! Thank you. I've isolated my brain from the API via Objectify. Thanks for the reply. "I'm not a smart man." Cheers, David -- You received this message because you are subscribed to the Google Groups "Google App Engine" group. To unsubscribe from this group and stop receiving emails

[google-appengine] using memcache without the datastore.

Is there a mechanism for using dedicated memory to "persist" data without writing to the datastore? Yes, it would suffer from flushes, that's OK. David -- You received this message because you are subscribed to the Google Groups "Google App Engine" group. To unsubscribe from this group and s

[google-appengine] Re: Emergency!

Yep, this just got real. I just received an email from a customer that was preparing a presentation for his company about my service's reliability. Guess what? GAE does a face-plant and makes me look like a total wheezer. Thanks a ton, GAE team! Another sale, down the drain. My credibility is b

[google-appengine] Re: what is future of GAE?

42. Nice one! Just found my cassettes of the BBC radio production. -- You received this message because you are subscribed to the Google Groups "Google App Engine" group. To unsubscribe from this group and stop receiving emails from it, send an email to google-appengine+unsubscr...@googlegroups

[google-appengine] Re: major bug in live instance hours calculation

Yep, I'm seeing instance madness. I've been using 2 instances for months and months. The load on my app is quite consistent. Then about Oct 1, the instance craziness began. There were times where 6 instances where running and 0 were billed. Now I have 4 running and 2 instances billed. Isn't App

Re: [google-appengine] Re: Large numbers of Error 500 - log says (Error code 121) after only a few seconds.

I'm driving down to Denver for the CEDIA show in a couple of hours. I dread showing my application to customers due to the current instabilities. Can you believe this!? David -- You received this message because you are subscribed to the Google Groups "Google App Engine" group. To unsubscribe

[google-appengine] Instances spinning up and down - website totally unreliable...

You are not alone. This problem has embarrassed me in front of customers. I'm not amused. David -- You received this message because you are subscribed to the Google Groups "Google App Engine" group. To unsubscribe from this group and stop receiving emails from it, send an email to google-ap

[google-appengine] Large numbers of Error 500 - log says (Error code 121) after only a few seconds.

I'm seeing this too. The latest update from the downtime notify group says that they have fixed the problem. I reply, "Sir, you are mistaken. The problem persists!" Wtf? David -- You received this message because you are subscribed to the Google Groups "Google App Engine" group. To unsubscri

[google-appengine] Absolutely red-faced by app engine errors during customer visit today.

Sure, unicorns are cute. However, during a demo at a customer site today in Boulder, my site coughed up errors repeatedly. (Reload, reload, reload, "Oh now it works! See!" what crap.) The main reason the customer had called my company was that they wanted a more *reliable* service. GAEJ's rec

[google-appengine] Re: GAE with major problems currently

Pear shaped for sure. David -- You received this message because you are subscribed to the Google Groups "Google App Engine" group. To unsubscribe from this group and stop receiving emails from it, send an email to google-appengine+unsubscr...@googlegroups.com. To post to this group, send email

[google-appengine] Re: Lots of warmup requests

Lots of warmups started for me about 5 days ago. It settled down for a day. Now it's gone pear shaped again. David -- You received this message because you are subscribed to the Google Groups "Google App Engine" group. To unsubscribe from this group and stop receiving emails from it, send an

Re: [google-appengine] GAE/J instances not shutting down as expected

Of course it did not last. 3 days of this new behavior. 1 day of reversion to previous characteristics, now back to the new behavior. H. David -- You received this message because you are subscribed to the Google Groups "Google App Engine" group. To unsubscribe from this group and stop rece

Re: [google-appengine] GAE/J instances not shutting down as expected

Check this out. New scheduler behavior is sweet, starting at about 1.25 days ago. > > And here's the memory usage.

Re: [google-appengine] GAE/J instances not shutting down as expected

I'm also seeing new scheduler behavior since MDT 8/28/2013. Not one instance has been torn down since then. No user facing requests have encountered a delay due to cranking up an instance. Sweet huh? Can't wait to see what happens now that my memory leaks accumulate without being "reset."

[google-appengine] Re: cron task not running. No errors in log. Huh!?

Might the task queue latency be relevant? Here's the status over the recent interval: Oh, and I found plenty of "Dead Man's Switch" services. But none that can be reset by a URLFetch. And none wit

[google-appengine] cron task not running. No errors in log. Huh!?

I have a cron task that is run every 5 minutes. From this chart of requests/sec over the past 3 hours you can see that it has failed to run several times. The problem is particularly heinous within the past hour.

[google-appengine] Re: 100% URL Fetch Failure from 2013-07-05 20:15:34 to 2013-07-05 22:34:30 MDT

Come on now. No response? At least try to blame this on me. David -- You received this message because you are subscribed to the Google Groups "Google App Engine" group. To unsubscribe from this group and stop receiving emails from it, send an email to google-appengine+unsubscr...@googlegroup

[google-appengine] Re: 100% URL Fetch Failure from 2013-07-05 20:15:34 to 2013-07-05 22:34:30 MDT

I found this on the System Status Page (classified as a green "everything's hunky dory" check mark.) This chart,"Measures the latency, in milliseconds, of a urlfetch API call to fetch Google.com."

[google-appengine] Re: 100% URL Fetch Failure from 2013-07-05 20:15:34 to 2013-07-05 22:34:30 MDT

Check it out. I actually found this on the System Status Page (classified as a pretty green "everything's hunky dory" check mark). David -- You received this message because you are subscribed

[google-appengine] 100% URL Fetch Failure from 2013-07-05 20:15:34 to 2013-07-05 22:34:30 MDT

I have a couple of apps on GAEJ-HRD. One app, let's call it the "client" runs a cron task every 5 minutes. That task performs URL fetches to another app of mine, let's call it the "server". Starting at 2013-07-05 20:15:34 MDT, 100% of the URL fetches failed. My re-try loops failed each time, ul

[google-appengine] Re: 90% of cron tasks failing with Error Code 121. Upset my customers are. Hosed I am.

oops.. meant to finish with: I found that: 1) I killed the only instance. 2) An hour or so later, memory usage dropped. 3) Errors ceased. Is this approx 75MB the normal usage by my app, and any excess would be a leak? Thanks! David -- You received this message because you are subscribed to th

[google-appengine] Re: 90% of cron tasks failing with Error Code 121. Upset my customers are. Hosed I am.

Here's what I've found: Does this indicate leaks? Is the Memory Usage plot on a per instance basis? Total memory used by all instances? I found that: I killed the only instance Memory usage dropp

Re: [google-appengine] Re: Flood of warm up requests!

This plot of number of instances is coincident with the failure of nearly all cron tasks: I would NEVER re-deploy under such questionable circumstances. Yet, someone needs to fix this (&(*^%

[google-appengine] Re: 90% of cron tasks failing with Error Code 121. Upset my customers are. Hosed I am.

And yet another, different, Error Code has appeared: *sigh* The only words I can think of now, were those uttered by Mr. Creosote: "Bring me a bucket!" David -- You received this message bec

[google-appengine] Re: 90% of cron tasks failing with Error Code 121. Upset my customers are. Hosed I am.

A new failure mode has appeared: Gee Wilikers! David -- You received this message because you are subscribed to the Google Groups "Google App Engine" group. To unsubscribe from this group and s

[google-appengine] 90% of cron tasks failing with Error Code 121. Upset my customers are. Hosed I am.

Starting at about MDT on 6/26/2013, about 90% of my Java HRD cron tasks have failed with Error Code 121. To wit: *This has crippled the primary service provided by my company.* I implore

[google-appengine] Re: Help! (GAJ) Cron jobs not started from 23:39 on 6/21 until 01:47 on 6/22. WTF?

Status update after reading Vinny's post: 1) Reading about Compute Engine. 2) Deep fryer is heating up. (For chicken and waffles.) 3) Sending remaining unicorns out for a Spa day. 4) Hope: restored; Anxiety: diminished. David -- You received this message because you are subscribed to the Goo

[google-appengine] Help! (GAJ) Cron jobs not started from 23:39 on 6/21 until 01:47 on 6/22. WTF?

Woke up this morning to find that my cron jobs were not running from 23:39 on 6/21 until 01:47 on 6/22. A Cron Job is configured to run every 5 minutes. The logs show: (note the missing activity after 23:29)

Re: [google-appengine] How many re-tries should I wrap my (failing) URL fetches in?

Hey Jeff, Urlfetch failures have been increasing in frequency lately. This is a fetch from another appengine app of mine. I have been receiving emails almost daily from the GAE team about problems with backends and urlfetches. How you been, man? David -- You received this message because you a

Re: [google-appengine] How many re-tries should I wrap my (failing) URL fetches in?

My overnight tests show that N=2 is not sufficient. I'll bump it up to 4. Do you use: Thread.sleep() ? David -- You received this message because you are subscribed to the Google Groups "Google App Engine" group. To unsubscribe from this group and stop receiving emails from it, send an email

[google-appengine] How many re-tries should I wrap my (failing) URL fetches in?

(Never end a topic with a preposition :) So, I just love writing and deploying code on-the-fly to cope with App Engine's failings. My question is, how many re-tries do you guys do before punting on a URL fetch? Infinite loop that just times out? N, where N is large? Cheers, (no, I take that b

Re: [google-appengine] Re: Deployments issues

App Engine has definitely gone pear-shaped. David -- You received this message because you are subscribed to the Google Groups "Google App Engine" group. To unsubscribe from this group and stop receiving emails from it, send an email to google-appengine+unsubscr...@googlegroups.com. To post to

Re: [google-appengine] Re: Bad news for GAE/Java from Google I/O

I suspect that's the first and last time we'll be hearing from Matt on this topic. David -- You received this message because you are subscribed to the Google Groups "Google App Engine" group. To unsubscribe from this group and stop receiving emails from it, send an email to google-appengine+

Re: [google-appengine] Re: Resident instance not serving the traffic

Once again, clearly stated by Carl. I roll with the punches using a script that fetches dynamic pages to induce a large uniform load. Speaking of large uniform loads, I gotta go shovel out the unicorn pens. David -- You received this message because you are subscribed to the Google Groups "G

[google-appengine] Re: Resident instance not serving the traffic

aswath, Barry is absolutely correct when he says that, "Unless you can provide real verifiable evidence, there is probably little Google can do. They need something to investigate." However, don't waste your time on this issue. Collecting "real verifiable evidence" on the ever-changing schedul

Re: [google-appengine] Re: instances dying is a permanent states for datastore apps?

Dearest Rafael, You are living in a dream world if you think migrating to HRD will stop instances from dying prematurely. This is not a criticism! Purposeful rejection of reality will save you! Do not apply reason to the instance scheduler! Here, we call it a "faith-based" scheduler. Have you

Re: [google-appengine] Re: HUGE latency increase

Yep, I saw this too. No worries here. This is typical behavior. You will get used to it. Just chill and it will change. Probably for the worse. David On Friday, March 22, 2013 3:31:12 AM UTC-6, Naresh Talluri wrote: > app-id : beta-sb > > > im facing the issue with task queue's, throwing  

Re: [google-appengine] Re: instances dying is a permanent states for datastore apps?

You read the previous posts on this right? You are complaining about instances lasting an hour? I'd sacrifice my prize unicorn to get that! When service goes pear shaped, instances last seconds! Yes. This behavior will change. No. You can't predict when the change will occur. No. There's nothing

[google-appengine] Re: Converting Google visualization charts to PDF

Me too. (At your leisure.) On Wednesday, March 13, 2013 8:01:31 AM UTC-6, Manoj Kumar wrote: > Hi, > > > I was trying a lot to export(convert) visualization chart to PDF. But, I'm > not to do it. Is there any way to do that so? If so, let me know ASAP.  > > > Best regards > Manoj. Siripuram

[google-appengine] Re: Many cold start problems recently.

lt of all this is that I feel like a burn victim being sold Icy > Hot under the generic brand "Soothing Cream". On the upside, I can now > cancel my subscription to "Unicorns Weekly". > > > On Thursday, March 7, 2013 6:38:50 PM UTC-8, Cesium wrote: >>

[google-appengine] Re: Many cold start problems recently.

spect that Google lumps all such claims into the same "not understanding > what resident instances are supposed to do" bucket and ignores them. > > > - Kris > > On Wednesday, March 6, 2013 5:45:30 PM UTC-8, Cesium wrote:Tapir, > > > > This is an ongoin

[google-appengine] Re: Many cold start problems recently.

Tapir, This is an ongoing issue we have suffered with. Get used to it. There will be no (useful) response from G. David On Tuesday, March 5, 2013 6:52:28 PM UTC-7, Tapir wrote: > There is a resident instance obviously there. But the GAE scheduler often > ignores it totally and always creates a

[google-appengine] Re: Instances keep shutting down

And never, ever, feed your unicorns Starburst candy. David On Tuesday, March 5, 2013 4:12:08 PM UTC-7, vlad wrote: > Star this issue  > http://code.google.com/p/googleappengine/issues/detail?id=8931 -- You received this message because you are subscribed to the Google Groups "Google App Engine

[google-appengine] Re: Instances still getting killed and causing user 500's

To paraphrase johnP, "This afternoon is a serving train-wreck." My poor unicorns' tongues are raw from gorging on Sour Skittles(tm). David On Friday, March 1, 2013 7:32:29 PM UTC-7, Cesium wrote: > > I'm sure you noticed the question on this forum that Takashi di

[google-appengine] Re: Instances still getting killed and causing user 500's

I'm sure you noticed the question on this forum that Takashi did respond to. On Friday, March 1, 2013 11:47:21 AM UTC-7, Carl Schroeder wrote: > I am porting to Go. Then I care much less about the instance scheduler > committing unicorn genocide. > Almost done.  > > > RIP GAE/J, thanks for was

Re: [google-appengine] Re: Instances still getting killed and causing user 500's

are concerned, the most effective solution is to > > > offer prayers very sincerely every morning. > > > > > > http://code.google.com/p/googleappengine/issues/detail?id=8781 > > > > > > This issue has been around for a few weeks with no resolution or any &

[google-appengine] Re: Instances still getting killed and causing user 500's

A couple hours later, all is well. Instances are lasting. Latency is low. Thank you Mr. Sparkles. (burp). On Wednesday, February 27, 2013 6:45:50 PM UTC-7, Cesium wrote: > Oh Joy, > > Now the console charts have been erased. > > I'm losing it. > > Unicorn liver p

[google-appengine] Re: Instances still getting killed and causing user 500's

Oh Joy, Now the console charts have been erased. I'm losing it. Unicorn liver pate for dinner. David On Wednesday, February 27, 2013 6:10:37 PM UTC-7, Cesium wrote: > Starting about 16:30 Pacific time, my Java HRD Instances were shutting down > after just a few seconds. >

[google-appengine] Re: Instances still getting killed and causing user 500's

Starting about 16:30 Pacific time, my Java HRD Instances were shutting down after just a few seconds. Just as my rage reached class IV, serving returned to normal. I know this is an overreaction, but I may have to sacrifice a unicorn. Please, please, App Engine team, spare Mr. Sparkles. This

[google-appengine] Re: AppEngine not serving - Error Code 121

d advice.  Tossing the Skittles in the trash, and running off to buy some > Starburst. > > > > On Wednesday, February 27, 2013 12:52:45 PM UTC-8, Cesium wrote: > Working fine now. > I found the problem. > I fed the unicorns Starburst instead of Skittles. > What an abbe

[google-appengine] Re: AppEngine not serving - Error Code 121

Working fine now. I found the problem. I fed the unicorns Starburst instead of Skittles. What an abbey-lubber! David On Wednesday, February 27, 2013 1:27:57 PM UTC-7, Cesium wrote: > My app is down! > > > 90% of calls return Error Code 121. > > > Is App Engin

[google-appengine] Re: AppEngine not serving - Error Code 121

My app is down! 90% of calls return Error Code 121. Is App Engine down? David -- You received this message because you are subscribed to the Google Groups "Google App Engine" group. To unsubscribe from this group and stop receiving emails from it, send an email to google-appengine+unsubscr..

[google-appengine] Re: Lots of user-facing loading requests

re killed almost immediately. > > > On Tuesday, January 22, 2013 11:16:51 PM UTC+1, Cesium wrote: >> >> Step 1: Sprinkle sour Skittles on the floor. (Sour, NOT regular Skittles.) >> Step 2: Wait for Google to release the unicorns for feeding. >> Step 3: When unicor

[google-appengine] Re: Lots of user-facing loading requests

scheduler's schizophrenic behavior! I did nothing! David On Tuesday, January 22, 2013 3:09:54 PM UTC-7, Francois Masurel wrote: > > Great ! But how did you get there? > > François > > > On Tuesday, January 22, 2013 5:28:48 PM UTC+1, Cesium wrote: >> >> For the

[google-appengine] Re: Lots of user-facing loading requests

For the record: Now my app is running so smooth on a single instance. No new instances being created. Latency is low. My depression is gone. Now, I am truly gobsmacked. David -- You received this message because you are subscribed to the Google Groups "Google App Engine" group. To view this

[google-appengine] Re: Lots of user-facing loading requests

I am also writing a "pepper script" today. -- 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/-/J7eDgV8iYqgJ. To post to this group, send email to googl

[google-appengine] Re: Lots of user-facing loading requests

Here we go again! My low traffic app has been running great for the past couple of weeks. Now I am seeing new instances being created every few minutes. Again, we have a change in the scheduler behavior for low traffic apps. Last time this happened I threw a fit. This time I am saddened and de

Re: [google-appengine] GAE Monitoring From Third Party

Brandon, What graphing routine makes the nifty plots on your monitoring page? David On Tuesday, January 15, 2013 11:05:00 PM UTC-7, Nickolas Daskalou wrote: > That's great, thanks Brandon. > > > Nick > > > > > > On 16 January 2013 15:29, Brandon Wirtz wrote: > > > > > > We are makin

Re: [google-appengine] Re: Urgent, Need Help: Instances are shutting down after a couple minutes of inactivity.

/msg/google-appengine/_znmrJwFMuM/V2epYOQ19L4J >>>>> >>>>> https://groups.google.com/d/topic/google-appengine/hg3BH8WOGWA/discussion >>>>> >>>>> https://groups.google.com/d/topic/google-appengine/UN5oCWkPsaA/discussion >>>>> >

Re: [google-appengine] Re: Urgent, Need Help: Instances are shutting down after a couple minutes of inactivity.

Ready for this? Now, a single instance survives for hours and hours, happily serving requests with the usual low latency response time. This is just what Sir Brandon wrote about. Mysterious changes in the system's behavior. I should note that I sprinkled rainbow Skittles across the floor to at

[google-appengine] Re: Urgent, Need Help: Instances are shutting down after a couple minutes of inactivity.

Thanks for putting the stress in my vacation this week, Appengine Team. David -- 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/-/1GsZFmLdX2gJ. To pos

[google-appengine] Re: Urgent, Need Help: Instances are shutting down after a couple minutes of inactivity.

What chaps my hide is the unannounced CHANGE in the behavior (for my app). I have been running for months with a single instance and no problems. Then, it breaks. No warning. No feedback. No drinks. No dinner. Nada. I have stayed out of the discussion because all was well. Oh, and, Takashi, don

[google-appengine] Re: Urgent, Need Help: Instances are shutting down after a couple minutes of inactivity.

I changed my settings to have 3 resident instances. I still see long latency when the scheduler creates new instances, rather than using the resident instances. The GAE scheduler behavior at low request rates is odd, and counterintuitive. But we knew that didn't we? David -- You received this

[google-appengine] Re: Urgent, Need Help: Instances are shutting down after a couple minutes of inactivity.

I fear that Sir Brandon has given us a fair assesment of GAE and GAE support. The unicorns have left the building. David -- 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/

[google-appengine] Urgent, Need Help: Instances are shutting down after a couple minutes of inactivity.

On Dec 16, something changed. Now, instances do not survive more than a couple minutes of inactivity (no incoming requests). Thus, low traffic applications see long latency since a new instance is created for the request. This is disastrous for my application (and customers). Can someone plea

[google-appengine] Re: System reset 8 hours ago. Instances now being shutdown after 2 mins of no requests.

Ok, Now the long lived instance is gone. New instances are living no longer than a couple minutes. This is really bad. David -- 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.

[google-appengine] Re: System reset 8 hours ago. Instances now being shutdown after 2 mins of no requests.

So now I look at the dashboard and there IS data going back several days! The list of instances shows an instance that is 11 hours old! I swear it was not there an hour ago. *sigh* David -- You received this message because you are subscribed to the Google Groups "Google App Engine" group. To

[google-appengine] System reset 8 hours ago. Instances now being shutdown after 2 mins of no requests.

My application dashboard shows a mysterious system reset (meaning no data prior to) about 8 hours ago. Since then, instances are being shutdown after about 2 mins of no requests. This new behavior negatively impacts our product. Of course we've made no changes to our app settings over the past

[google-appengine] Re: GAE keeps starting new instances causing lots of user facing loading requests

I can confirm that we are observing increased latency and bothersome startups of new instances. David On Thursday, November 29, 2012 9:35:29 AM UTC-7, Nik Eleftheriou wrote: > Right about the time i noticed the scheduler had started cycling instances > every 3-4 minutes, I also noticed that our

Re: [google-appengine] Re: Update on our GAE Experience

Alex wrote: > What I'm saying is, guys like Brandon can move off/to Rackspace, AWS > and what have you, but it's often not a solution - just delaying > something that comes back later. All we do is running huge and complex > Turing machines after all. Well, unless it's a neural network thing

Re: [google-appengine] Re: Update on our GAE Experience

Finally! The seeds of an Alex-Brandon dust-up appear! This group has been so BORING! David Brandon: All good points; well stated. -- 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.goo

Re: [google-appengine] Re: download

Lol. Nice one Barry. david -- 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/-/jpOOkdpD5mAJ. To post to this group, send email to google-appengine@goo

[google-appengine] Min-Idle-Instances vs Min-Instances

So, I've studied the recommended thread, with explanations from lead engineer Jon McAlister: https://groups.google.com/d/msg/google-appengine/nRtzGtG9790/hLS16qux_04J and Johan wrote: > If you want another behavior like a new slider for Min-Instances please > fill a new feature request. Ha

Re: [google-appengine] Re: How to blacklist planet-lab.org?

G'day Kate, Did the hoons end up in the divvy van? I'd be gobsmacked if you didn't leave them tall poppies all stonkered. At least demand a few tinnies of amber fluid. David PS Just testing my new RESTful API: convertposttoaussiespeak.appspot.com -- You received this message because you are su

[google-appengine] Re: Anybody interested in a Datastore Manager for GAE?

After studying your mockup, I would be very interested in joining you for lunch at Mortons. Wow! -- 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/-/0

Re: [google-appengine] APP DOWN due to some sort of undocumented Google security system

Chris, I am using GAE for my startup and it's just freakin' awesome. I don't use frameworks. I don't use CDNs (whatever those are!?). I don't use SSL. Just MVP and Objectify, and it flat out rocks. Daily, I pee in my pants with excitement. My customers are thrilled. (Both of them). David (Th

Re: [google-appengine] APP DOWN due to some sort of undocumented Google security system

I hate it when Mommy and Daddy fight. -- 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/-/4QHhaqkMOPUJ. To post to this group, send email to google-app

Re: [google-appengine] Re: How will GAE handle the leap second at 23:59:60 on 6/30/2012?

Refactoring our code would be too expensive. Let's just ignore the leap second and hope for the best. David -- You received this message because you are subscribed to the Google Groups "Google App Engine" group. To view this discussion on th

Re: [google-appengine] Re: How will GAE handle the leap second at 23:59:60 on 6/30/2012?

Yet more heartbreak due to engineers not handling the corner cases. David -- You received this message because you are subscribed to the Google Groups "Google App Engine" gr

Re: [google-appengine] Re: How will GAE handle the leap second at 23:59:60 on 6/30/2012?

Hi Simon, You wrote: I'm really surprised by the servers being within 500ms of each other, to be > honest. > > I've got a timesheet product on GAE and I've had clock skew of more than a > minute between some instances, although it's fairly rare that it's anywhere > near that large and it's a

Re: [google-appengine] Re: How will GAE handle the leap second at 23:59:60 on 6/30/2012?

Hey Jeff, Think of, for example, a global network of sensors measuring geo-physical phenomena. They need to be synchronized. The maximum uncertainly is determined by the phenomenon being measured. It all boiled down to needing a time server on port 80 whose difference from UTC was less than ab

[google-appengine] Re: How will GAE handle the leap second at 23:59:60 on 6/30/2012?

That's interesting reading from the Site Reliability Engineering Group (SREG). I read: > Having accurate time is critical to everything we do at Google. > Agreed. I also read: > Usually when a leap second is almost due, the NTP protocol says a server > must indicate this to its clients by s

[google-appengine] How will GAE handle the leap second at 23:59:60 on 6/30/2012?

Here's a summary of the problem: The UNIX leap second mess. How will App Engine's servers handle the leap second? David -- You received this message because you are subscribed to the Google Groups "Google App Engine" group. To vie

Re: [google-appengine] Re: Java instance startup time out of control

I'm really liking Brandon's conclusions. David -- 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/-/qAG4p6uKDLIJ. To post to this group, send email to g

Re: [google-appengine] Re: Java instance startup time out of control

Dang Jeff, This sounds brutal. The only aspect I could test and collect data on is Objectify. I'm not really sure what most of those other technologies are. If there is something I could set up in parallel for testing (something I could actually understand), just holler'. David PS, maybe som

Re: [google-appengine] If your bill shoots up due to increased latency, you may not be refunded the charges incurred

Sigh, Brandon wrote: > The variance between my "identical" requests is less than 10%. > Yea, me too. Except when it ain't. I went class 4 ape$hit a couple of weeks ago, when I saw latencies for my app increase by 50x. That's 5000%. Check out the last 30 days of operation (milliseconds per r

Re: [google-appengine] Service Failure - all instances restarted simultaneously

Thanks Michael, Me too. I use HRD Java and Objectify. I am seeing some crazy start times. I think I will deploy an application that is specifically designed to monitor instance lifespan and start up times. If you have any design ideas, let me have 'em. I'll start on it later in the week. Davi

Re: [google-appengine] Service Failure - all instances restarted simultaneously

Hi Takashi, You wrote: > ...it is very important to keep your application fast even on the loading > request in order to minimize the damage to your system during such serving > changes. Can you refer me to some guidelines to keep my application fast even on the loading request? I have no

[google-appengine] Re: Large latency spike, need assistance

Nathan, You called it a "processing speed bug". That feels like what I am seeing too. An almost trivial servlet that usually takes 30 milliseconds to run is taking as much as 2000 milliseconds. This is negatively impacting my capitalistic endeavors. David -- You received this message becaus

Re: [google-appengine] Huge execution times. DeadlineExceededException(s). Crushing Weltschmerz.

Hi Alex, First things first. I'm an idiot. The second reply comes in 3 MINUTES later, not 3 SECONDS. Let me chew on your suggestions a bit... David PS (Can I edit a previous post, rather than deleting it?) -- You received this message because you are subscribed to the Google Groups "Google

Re: [google-appengine] Huge execution times. DeadlineExceededException(s). Crushing Weltschmerz.

Hi Takashi, You wrote: Actually, in that timeframe, I can see that only loading requests of > your application had higher latencies. > Those kind of hiccups are supposed to be automatically addressed and > fixed swiftly(almost always faster than manual intervention like me > doing right now)

Re: [google-appengine] Huge execution times. DeadlineExceededException(s). Crushing Weltschmerz.

Hi Takashi, Thank you for your reply! You have taken the time to personally look into my issues and for that I am grateful. I promise to follow your suggestions. It may take me a couple of days to perform some tests. I will let you know if I have new questions. Best Regards, David -- You r

Re: [google-appengine] Huge execution times. DeadlineExceededException(s). Crushing Weltschmerz.

Hi Takashi, Thank you for your help! I sent you an email with some details. Cheers, David -- 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/-/hD6FC_

Re: [google-appengine] Stop tearing down my instances!

Hey Iein, Thank you for the reply! I sent you an email with some details. Cheers, David -- 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/-/VrxRBuGX

[google-appengine] Huge execution times. DeadlineExceededException(s). Crushing Weltschmerz.

I am seeing wild execution times for requests that nominally take 500ms. E.g., xxx.xxx.xxx.xxx - - [01/Jun/2012:07:21:08 -0700] "POST /xxx/sdtp?t=ACCESS_POINT_APP_DATA_UPLOAD HTTP/1.1" 200 64 - - "xxx.appspot.com" *ms=54346* cpu_ms=3858 api_cpu_ms=8 cpm_usd=0.107224 loading_request=1 pending_ms

Re: [google-appengine] Stop tearing down my instances!

A few hours ago, one app started to settle down: > > milliseconds per request: [image: Requests/Second (24 hrs)] But the app that makes the customers call my f%*#ing cell phone shows: milliseconds per request: [image: Requests/Second (24 hrs)] It appears both apps showed improvement about 5 ho

Re: [google-appengine] Stop tearing down my instances!

Smooth sailing for a month and a half. Billing enabled. Today, its going to hell in a tortilla for my customer facing apps, and my development apps. All have billing enabled. Is the appengine group at a team building retreat in Nappa? WTF? David -- You received this message because you are sub

Re: [google-appengine] Stop tearing down my instances!

OK, I've got 1 resident instance, and 2 dynamic instances. They are seeing and average of 0.006 Queries per Second (very light load). There are warm-up requests every 5 minutes or so. But, I am still seeing client transactions that cause an instance to be started. In the event that an existing in

Re: [google-appengine] Stop tearing down my instances!

Is that one of those things where you highlight parts of the screen. Then it says, "Thanks for your feedback, we probably won't get back to you." ? Yup, did that. David -- You received this message because you are subscribed to the Google Groups "Google App Engine" group. To view this discussio

  1   2   >