[google-appengine] Google App Engine's Team Dishonesty
Google app engine hello, Let me first specify that I am a paying app engine user for about 1.5 years. We, at my company, have developed an online restaurant takeout/ delivery ordering service running completely on the appengine. We currently serve over 50 restaurants in my home country, and are now expanding abroad with restaurants in Canada, Hungary, Belgium, UK, and more. Ever since the appengine's release from production a week ago, there has been 3 (!!!) major disruptions - On 7th for 45 minutes, yesterday for 30 minutes, and right now. I understand that failures occur, but specifying a "99.95%" and being so far from it is to me a major failure on the part of Google. To make matters worse, we, AppEngine's paying users, NEVER receive any explanations or descriptions of the cause of the failure, the solution and Google's efforts to prevent its returning occurance. Not by any means to compare, but EC2's team constantly admit and report ALL of the failures and their debriefing! And now for the "cherry on the top", and the reason I used the word 'dishonesty' - You remove any note of the disruption from System Status. For example, yesterday there was a disruption causing 40 secs (!!!) of latency in response. Today viewing the System Status, yesterday is marker with "No significant issues". That to me is dishonesty and a clear cut lie. Unfortunately, our service is now so deeply connect to the AppEngine framework that leaving this service is currently not an option, but I would definitively not advise or recommend anyone to use the AppEngine today, and my next product will definitely not run on the AppEngine. Regards, - Yoav. -- 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: Google App Engine's Team Dishonesty
Hello, Me again :) Yes, we are using HRD. Indeed since we moved to it (at least 4-5 months ago), things became stabler... stable enough? Good question. I have a monitoring SW (running on EC2) making a request every minute. In the past week this monitoring system gave me at least 2 errors per day and sometimes more (500 - Internal Server Error... and no, the request never reached our app. It fails before us). I know it seems like a very low number, but still I'd like to have one day without an error. (2 disappointed clients a day for me, as a very young start-up, can cause some very bad brand reputation). Regarding the dishonesty issue - It still amazes me that at times I see an "Investigating" or "Elevated" sign in the system status, sometimes 45 minutes of a very high Java latency, and the next day "No significant issues" on the previous day. I, and I'm guessing the rest of the people here, would really appreciate some kind of acknowledgment from Google that you have seen the issue, and didn't just "let it disappear" but rather investigated it, found the cause, and are performing steps to make sure it does reappear. Basically what I'm asking, and what I think everyone is asking here, is to know that there is someone to talk to. If you look back at the 'issues' site, you'll see many 'production' issues from people like me crying for help during downtime. These issues have gone unanswered even now, months after the issues. If you'll look at other monitoring sites you'll see that there is some kind of description of the issues as they happen. Now, I fully understand that during times of disruptions you guys are amazingly busy in trying to solve them, but perhaps just a word from a human-being and not an automated SW to show that we have someone there helping us, and perhaps, just perhaps an ETA on a solution? Thank you again, and sorry for the long posts - It is just frustrating having nothing to do during down times other then refreshing the status monitor and prying (last downtime, 45 minutes, I pryed to every religions' god - anything that can work, I don't discriminate during down times :) ) - Yoav On Nov 19, 11:55 pm, "Gregory D'alesandre" wrote: > Hello all, > > Trying to show an accurate and honest representation of the status of a > massive distributed service is a really hard technical challenge but an > even harder conceptual one. While your app might be showing higher latency > or errors that doesn't indicate a systematic issue with the whole service. > For instance, the main reason we are encouraging customers to move to HRD > is because M/S is dependent on single BigTable tablets, this means you can > have lots of issues when there is absolutely nothing wrong systematically > with GAE. There was a small service disruption (on the order of minutes) > in some HRD apps recently when a datacenter was having systematic issues so > we have to re-ruote that traffic. But, it didn't show up on the status > site because it was a short disruption that only affected a small portion > of users. > > The upshot of this is that our status site gives a general sense of how App > Engine is running but that doesn't show whether your app is experiencing > issues or not, it just shows whether the probes we are using to generate > the information are having issues. So, at times, when it says there is a > problem initially and then it disappears it is usually because a prober app > was having an issue but it was not a large-scale issue for all of GAE. We > are not trying to hide issues, quite the contrary when there is a > large-scale systematic issue we have a policy of doing post-mortems and > posting them publicly, So, if your app is having an issue and the status > site looks fine, this is probably not a lie but rather an artifact of how > we show status for the system. > > We are looking into ways to improve this to be more useful but I hope that > helps clarify why you see what you see. > > Yoav, I never saw a response as to whether you are using HRD or not, the > 99.95% SLA only applies to HRD because we know M/S is going to have issues. > As always, thanks for the feedback! > > Greg D'Alesandre > Senior Product Manager, Google App Engine > > > > > > > > On Fri, Nov 18, 2011 at 7:07 PM, WallyDD wrote: > > I have always wondered the same thing. One minute there is an issue, a > > few days later it never happened. > > Google is far from alone with such issues which is why there are > > websites/services that monitor cloud status. > > > It may be a little unfair calling the app engine team dishonest. > > Trying to change something in a large organization can be a very > > unrew
[google-appengine] Re: Google App Engine's Team Dishonesty
OK, ok, ok, so we don't talk in theory (and to answer one question - the errors are of requests that don't reach our app. They fail before): Example 1 http://code.google.com/status/appengine/detail/serving-java/2011/11/15#ae-trust-detail-helloworld-secure-get-java-error_rate - First look at the general console, you will see no mentioning of this event. - OK. Failures happen. Now, why? what is done? Who is working on it? During the failure, when will it be fixed? Any kind of online information so I won't feel alone in the dark! Trust me, I'd feel better knowing that someone brought his pet and it cut the power cord, and it will take 30 minutes to come back rather then nothing at all! Example 2 http://code.google.com/p/googleappengine/issues/detail?id=6274&can=5&colspec=ID%20Type%20Component%20Status%20Stars%20Summary%20Language%20Priority%20Owner%20Log This was during a 45 minute down-time (BTW, marked again as 'under investigation' after being marker as 'no significant issues' so kudos on the remark!) between the 5th and the 6th phone call I've received from restaurants wanting to leave my system. I think this was after I tried Tweeting app engine, and right before I was looking for Mr. Page's personal email address :) - Is there anyone to talk to during these times or do I HAVE to sign up for the $500 program just to have someone tell me when will the problem be solved? I don't think GAE teams is anything but very very professional. I don't think I would ever manage to really set up such a wonderful service. I just think that their customer-relationship needs a bit of work (which will definitely result in more people joining and staying!). - Yoav. On Nov 20, 2:01 am, "Brandon Wirtz" wrote: > We may just have different locations for where our apps are... But we have > uptime monitoring on several dozen domains and they get checked every 5 > minutes, so we are checked something like every 15 seconds for the uptime of > our primary app. We've had 90 seconds or so of downtime, and during that > time static files still served and requests that took less than 20 seconds > to fill were served. > > We have seen issues where long time to fill requests had high fail rates. > We have also seen that if we set the application settings to have too few > idle instances that we got a LOT of 500 errors. > > Do you have your app set to automatic? Or have you clamped your Apps number > of idle instances. How long does a typical request take to fill? How about > a "long" request. > > Some of your downtime may be your own fault, not GAE's. Don't know that for > sure, but when my multiple apps don't exhibit a behavior I assume that the > issue isn't system wide, but localized to something a given user is doing. > > > > > > > > -Original Message- > From: google-appengine@googlegroups.com > > [mailto:google-appengine@googlegroups.com] On Behalf Of trilok > Sent: Saturday, November 19, 2011 3:42 PM > To: Google App Engine > Subject: [google-appengine] Re: Google App Engine's Team Dishonesty > > Hello, > > Me again :) > > Yes, we are using HRD. Indeed since we moved to it (at least 4-5 months > ago), things became stabler... stable enough? Good question. > > I have a monitoring SW (running on EC2) making a request every minute. > In the past week this monitoring system gave me at least 2 errors per day > and sometimes more (500 - Internal Server Error... and no, the request never > reached our app. It fails before us). I know it seems like a very low > number, but still I'd like to have one day without an error. (2 disappointed > clients a day for me, as a very young start-up, can cause some very bad > brand reputation). > > Regarding the dishonesty issue - It still amazes me that at times I see an > "Investigating" or "Elevated" sign in the system status, sometimes 45 > minutes of a very high Java latency, and the next day "No significant > issues" on the previous day. I, and I'm guessing the rest of the people > here, would really appreciate some kind of acknowledgment from Google that > you have seen the issue, and didn't just "let it disappear" but rather > investigated it, found the cause, and are performing steps to make sure it > does reappear. > > Basically what I'm asking, and what I think everyone is asking here, is to > know that there is someone to talk to. If you look back at the 'issues' > site, you'll see many 'production' issues from people like me crying for > help during downtime. These issues have gone unanswered even now, months > after the issues. If you'll look at
[google-appengine] Re: Google App Engine's Team Dishonesty
Mr. Wirtz, Thank you for your recommendation! Unfortunately I would really not want this conversation to move to the 'why I get so many errors' realm, and as you can clearly see the examples I have given above are system wide daily errors rather then application specific errors. My original post specified 3 major system wide disruptions, but the rest of my post talked mainly of GAE team's handling of these disruptions. I perfectly know that there are errors caused by my company's system, and by our configuration - I am sure there are still many things we can do to make them better (Thank god we are far from 10% error rate on our account). I have no doubt that 99% of the time errors are caused by users' bugs rather then GAE's production issues. I would really want this conversation to move something in Google to make their handling of the system wide errors as transparent and honest as possible, to help us communicate as much information to our clients as we can. (Mr. D'alesandre, are you reading this? Am I achieving my goal somehow? :) ) I hope you understand why I am 'avoiding' your question, as I simply think it can take us out of the path of to the discussion I am trying to advance (Yes, I am limiting my max number of instances, and yes I know it can cause errors but I almost always have at least 2 idle instances, and my errors are at times where traffic is not at its maximum). - Yoav. On Nov 20, 2:58 am, "Brandon Wirtz" wrote: > You avoided my question. Have you limited max idle instances. > > Failure before reaching the app can be that you have no available instances > to handle the request which was why I was asking if you had set max idle > instances. If those are set wrong you will get 500 errors up the wazoo and > never see a single error in your log. I have helped several people who > thought they were saving money by setting those to very low numbers only to > find out they were losing 10% of their traffic to errors. > > > > > > > > -Original Message- > From: google-appengine@googlegroups.com > > [mailto:google-appengine@googlegroups.com] On Behalf Of trilok > Sent: Saturday, November 19, 2011 4:20 PM > To: Google App Engine > Subject: [google-appengine] Re: Google App Engine's Team Dishonesty > > OK, ok, ok, so we don't talk in theory (and to answer one question - the > errors are of requests that don't reach our app. They fail > before): -- 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: Google App Engine's Team Dishonesty
Mr Wirtz, You have not read my response. All of the examples I have given are Google issues since they are presented in the system status. I do know when my system is down for my fault and when it is down on Google's fault. If you dive into the system status you will see that even by their account they do not meet the SLA (Current availability is 98.92%. FAR from 99.95%). Again, my real issue is that Google not only does not meet their SLA, but that they do not communicate the issues transparently to their users. Facts are these: 1. Google do not meet their SLA (again, look at their stated current availability in the system status). 2. When they are down on their fault, I have no way of knowing when is the problem going to be fixed, and how are they preventing it in the future. If I do not know the answers to those questions, how can I communicate stability to my clients? What do I tell my paying clients when they ask me 'when is the system going to be up again'? I am begging you again, do now make it a "who's fault is it that my system is down" issue! Sadly I already think that you've diverted the conversation to a point where I won't get any answers now Bottom line I would like Greg to answer: How can I continue using the GAE when I do not get transparency regarding Google related down times (during or after)? - Yoav. On Nov 20, 4:07 am, "Brandon Wirtz" wrote: > You sited outage numbers greater than what Greg did. If your app was down > for your own fault then it is NOT a google issue. > > If less than 1% experienced an outage of less than 5 minutes, and those apps > were idle then the number of "lost" pages was likely even lower. > > You said they were not meeting SLA, and Not Reporting. But if your numbers > are wrong, then we don't know that is the case. You can't call Google out, > AND not diagnose if the problem is YOUR fault. -- 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: Google App Engine's Team Dishonesty
Although I repeatedly asked you not to take this conversation to "Who's fault is the downtime", you still do so! Again, my problem is that when it is Google's fault, there's no one to talk to - Can you argue anything relevant to this point please? Amazon had a week downtime, but THERE WAS SOMEONE TO TALK TO! Whenever Amazon is done I receive an email from them telling me why, and how they solved it. I would be happy to continue the conversation of "is google meeting their SLA" in private. But read the subject of this email - You can't argue that on the 11th of November there was a serious issue which is not represented in the system status, and that we have not been informed any of! Regarding the points you have mentioned: 1. For 45minutes, 30% of errors, is to me 45 minutes of downtime. Since it happens during evening time when thousands of people enter my site to order lunch, and 30% of them need to refresh the site to see the welcome page and the rest suffer latency, I see it as 45 minutes. (I agree, it could be worse, but it is still bad for my brand name). 2. By definition you cannot have the uptime you talked about when Google themselves say that they have a 98.92% up time! Unless you do not have traffic during those times, which is cool for you, but we have traffic to our site all of the time. - Yoav. On Nov 20, 10:44 am, "Brandon Wirtz" wrote: > I read your response. > > I don't think you read the graphs you sent. > For 45minutes they were at 30% errors. That only counts as 15 minutes of > downtime. And since it appears that only polls once every 5 min or so I'm > not sure what that means for SLA. > > You spoke of downtimes you had that weren't reported elsewhere. And you > said that you know it was GAE's fault because they didn't hit your App. I'm > saying that your "downtime" may have been misconfiguration. > > Also even if you are correct that 99.5 isn't being met since they are at > 98.2 or something along those lines, it is early in the yearly average. > > I'm all for calling people out when they have made mistakes, but my uptime > thus far is north of 99% and is likely north of 99.75% Amazon had nearly a > week of down time, they will be 2 years getting that back to an average of > 99.5. > > > > > > > > -Original Message- > From: google-appengine@googlegroups.com > > [mailto:google-appengine@googlegroups.com] On Behalf Of trilok > Sent: Sunday, November 20, 2011 12:03 AM > To: Google App Engine > Subject: [google-appengine] Re: Google App Engine's Team Dishonesty > > Mr Wirtz, > > You have not read my response. > > All of the examples I have given are Google issues since they are presented > in the system status. > > I do know when my system is down for my fault and when it is down on > Google's fault. If you dive into the system status you will see that even by > their account they do not meet the SLA (Current availability is 98.92%. FAR > from 99.95%). > > Again, my real issue is that Google not only does not meet their SLA, but > that they do not communicate the issues transparently to their users. > > Facts are these: > > 1. Google do not meet their SLA (again, look at their stated current > availability in the system status). > > 2. When they are down on their fault, I have no way of knowing when is the > problem going to be fixed, and how are they preventing it in the future. If > I do not know the answers to those questions, how can I communicate > stability to my clients? What do I tell my paying clients when they ask me > 'when is the system going to be up again'? > > I am begging you again, do now make it a "who's fault is it that my system > is down" issue! Sadly I already think that you've diverted the conversation > to a point where I won't get any answers now > > Bottom line I would like Greg to answer: How can I continue using the GAE > when I do not get transparency regarding Google related down times (during > or after)? > > - Yoav. > > On Nov 20, 4:07 am, "Brandon Wirtz" wrote: > > You sited outage numbers greater than what Greg did. If your app was > > down for your own fault then it is NOT a google issue. > > > If less than 1% experienced an outage of less than 5 minutes, and > > those apps were idle then the number of "lost" pages was likely even > lower. > > > You said they were not meeting SLA, and Not Reporting. But if your > > numbers are wrong, then we don't know that is the case. You can't > > call Google out, AND not diagnose if the problem is YOUR fault. > > -- > You received this message because y
[google-appengine] Re: Google App Engine's Team Dishonesty
Brandon, read my original post - the dishonesty is regarding the fact that one day they say that the service has disruption, and the next they show that they don't. Not who's fault is that my app is down. When I call support I want to know how long will it take them approximately to solve the problem so I have something to tell my clients. I'm a bloody paying customer, I deserve that, like my paying customers deserve it from me. It is clear to me you don't run a B2B business, so please don't comment on things you do not understand. Since you fail to read my posts and understand them (read the first line of this post) I can only ask you to mind your own business and stop wasting my time with unrelated answers to my posts. Can we SOMEHOW return to the subject at hand - Transparency? Or is this a lost cause because of people like this guy? On Nov 20, 11:26 am, "Brandon Wirtz" wrote: > Yes. Because the thread is "GAE team is dishonest" > > If their honesty is in contention then who's fault your app is down is > relevant. > > Yes I can have higher than 98.92 because not everyone was down during those > times. Plus Edge Cache can serve up to 60% of my traffic for short periods > of time, so even during an outage I can be partially up. Also Static files > haven't had any downtime. > > As to the "someone you can call" if everything is down, calling someone > doesn't help. Even if you had a premier app, the conversation would go "Hey > we are down" "Yep we lost all of the datacenter you are in" "can you get me > back up?" "yep when everyone else comes back up" > > What a support account gets you is things like "Hey I'm on Python 2.7 and > Thread Safe seems to be giving me 2+2 = 5 and it takes 50 seconds to > calculate it" Or the ability to call someone and say "hey I need to alias a > bunch of apps on to each other and merge the data, is there a best practice > for that?" > > Would an in dashboard SLA counter be awesome? Yes. But you are delusional > if you think Amazon has ever been forth coming about issues. > > > > > > > > -Original Message- > From: google-appengine@googlegroups.com > > [mailto:google-appengine@googlegroups.com] On Behalf Of trilok > Sent: Sunday, November 20, 2011 1:07 AM > To: Google App Engine > Subject: [google-appengine] Re: Google App Engine's Team Dishonesty > > Although I repeatedly asked you not to take this conversation to "Who's > fault is the downtime", you still do so! > > Again, my problem is that when it is Google's fault, there's no one to talk > to - Can you argue anything relevant to this point please? Amazon had a week > downtime, but THERE WAS SOMEONE TO TALK TO! Whenever Amazon is done I > receive an email from them telling me why, and how they solved it. > > I would be happy to continue the conversation of "is google meeting their > SLA" in private. But read the subject of this email - You can't argue that > on the 11th of November there was a serious issue which is not represented > in the system status, and that we have not been informed any of! > > Regarding the points you have mentioned: > > 1. For 45minutes, 30% of errors, is to me 45 minutes of downtime. > Since it happens during evening time when thousands of people enter my site > to order lunch, and 30% of them need to refresh the site to see the welcome > page and the rest suffer latency, I see it as 45 minutes. > (I agree, it could be worse, but it is still bad for my brand name). > > 2. By definition you cannot have the uptime you talked about when Google > themselves say that they have a 98.92% up time! Unless you do not have > traffic during those times, which is cool for you, but we have traffic to > our site all of the time. > > - Yoav. > > On Nov 20, 10:44 am, "Brandon Wirtz" wrote: > > I read your response. > > > I don't think you read the graphs you sent. > > For 45minutes they were at 30% errors. That only counts as 15 minutes > > of downtime. And since it appears that only polls once every 5 min or > > so I'm not sure what that means for SLA. > > > You spoke of downtimes you had that weren't reported elsewhere. And > > you said that you know it was GAE's fault because they didn't hit your > > App. I'm saying that your "downtime" may have been misconfiguration. > > > Also even if you are correct that 99.5 isn't being met since they are > > at > > 98.2 or something along those lines, it is early in the yearly average. > > > I'm all for calling people out when they ha
[google-appengine] Re: Google App Engine's Team Dishonesty
Oh, and you are not an "Ass, a Troll, an Idiot". I respect your excellent ambition to 'protect the innocent'. I agree my subject line was inflammatory to get a response, which it got. I have nothing but respect to the GAE team (as I said again and again and again). I am sorry to tell you but I rechecked the configurations and all the 500's I get and non of them are our fault. But lets put that aside. Now, Brandon, please tell me what will it take to return this discussion to the transparency issue? Respect my problems with Google, like people respect yours. On Nov 20, 11:55 am, trilok wrote: > Brandon, read my original post - the dishonesty is regarding the fact > that one day they say that the service has disruption, and the next > they show that they don't. Not who's fault is that my app is down. > > When I call support I want to know how long will it take them > approximately to solve the problem so I have something to tell my > clients. I'm a bloody paying customer, I deserve that, like my paying > customers deserve it from me. It is clear to me you don't run a B2B > business, so please don't comment on things you do not understand. > > Since you fail to read my posts and understand them (read the first > line of this post) I can only ask you to mind your own business and > stop wasting my time with unrelated answers to my posts. > > Can we SOMEHOW return to the subject at hand - Transparency? Or is > this a lost cause because of people like this guy? > > On Nov 20, 11:26 am, "Brandon Wirtz" wrote: > > > > > > > > > Yes. Because the thread is "GAE team is dishonest" > > > If their honesty is in contention then who's fault your app is down is > > relevant. > > > Yes I can have higher than 98.92 because not everyone was down during those > > times. Plus Edge Cache can serve up to 60% of my traffic for short periods > > of time, so even during an outage I can be partially up. Also Static files > > haven't had any downtime. > > > As to the "someone you can call" if everything is down, calling someone > > doesn't help. Even if you had a premier app, the conversation would go "Hey > > we are down" "Yep we lost all of the datacenter you are in" "can you get me > > back up?" "yep when everyone else comes back up" > > > What a support account gets you is things like "Hey I'm on Python 2.7 and > > Thread Safe seems to be giving me 2+2 = 5 and it takes 50 seconds to > > calculate it" Or the ability to call someone and say "hey I need to alias a > > bunch of apps on to each other and merge the data, is there a best practice > > for that?" > > > Would an in dashboard SLA counter be awesome? Yes. But you are delusional > > if you think Amazon has ever been forth coming about issues. > > > -Original Message- > > From: google-appengine@googlegroups.com > > > [mailto:google-appengine@googlegroups.com] On Behalf Of trilok > > Sent: Sunday, November 20, 2011 1:07 AM > > To: Google App Engine > > Subject: [google-appengine] Re: Google App Engine's Team Dishonesty > > > Although I repeatedly asked you not to take this conversation to "Who's > > fault is the downtime", you still do so! > > > Again, my problem is that when it is Google's fault, there's no one to talk > > to - Can you argue anything relevant to this point please? Amazon had a week > > downtime, but THERE WAS SOMEONE TO TALK TO! Whenever Amazon is done I > > receive an email from them telling me why, and how they solved it. > > > I would be happy to continue the conversation of "is google meeting their > > SLA" in private. But read the subject of this email - You can't argue that > > on the 11th of November there was a serious issue which is not represented > > in the system status, and that we have not been informed any of! > > > Regarding the points you have mentioned: > > > 1. For 45minutes, 30% of errors, is to me 45 minutes of downtime. > > Since it happens during evening time when thousands of people enter my site > > to order lunch, and 30% of them need to refresh the site to see the welcome > > page and the rest suffer latency, I see it as 45 minutes. > > (I agree, it could be worse, but it is still bad for my brand name). > > > 2. By definition you cannot have the uptime you talked about when Google > > themselves say that they have a 98.92% up time! Unless you do not have > > traffic during those times, which is cool for you, but we have traffic to > >
[google-appengine] Re: PCI DSS for AppEngine
Hey Koen, Did you ever manage to get your app approved? - Yoav. On Monday, November 1, 2010 2:48:57 PM UTC+2, Koen Bok wrote: > > Did anyone get their AppEngine app PCI DSS compliant? Is there a > company that can help out with this? > > Koen -- 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/-/pfVJ_AxUX7IJ. 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] Good feedback for today
Hi, As someone who in past spoke against GAE specifically in regards to the information received during downtime, i gotta say: What an improvement! The hourly updated forum and answers in this group are a great leap forward compared to the silence we had in the past during downtimes. Great job Google (IMHO)! - Y. -- 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/-/K7YGTXzLiH8J. 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] Sandy
Hey, Just to make sure, are we to expect any issues from hurricane Sandy? Thanks! - Yoav -- 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/-/GuZWxbmULMsJ. 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] Image service - timeout
Hey,
For last day we've been getting a lot of timeouts ("DeadlineExceededException")
while trying to access gae's image service (imageService.getServingUrl).
application id: spice-prod
Are there any issues with this service at the moment?
Thanks,
- Yoav.
--
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/-/bp92W3S1hF0J.
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] Anyone experiencing problems right now?
Our instances keep crashing.Tons of 500s (internal server errors). Started a few minutes ago. Anyone experiencing the same? -- 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/-/0G81qmgz3tYJ. 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.
