There just needs to be more information. This is a service people pay money for. Where are the explanations of todays errors? Adding an issue at the tracker almost always goes unnoticed - writing in these (three different) forum groups almost always goes unnoticed.
Can we expect these 500 error that have been coming and going for months to be fixed one day, or are we supposed to pull our apps and rewrite them into something that is less scalable but -actually- working? This is not supposed to be hard. Everybody are confined to java and python - nothing more, errors can be contained. No filesystem, everything in a database which prohibit any operation that look like join and has indexes for everything that can be fetched except if one actually knows the unique key. With this in mind, things are simple. Its not supposed to be that hard - if you can't do what companies that allow SQL and multiple languages can, then please buy a hosting company and get some best practices from there. You've got the money - you've got our money, as we pay for the service. If you need more money to make it work upp the prices a little, because -random- 500 errors are unacceptable for everybody. A few answers and a few pieces of information would be nice. Thank you. On May 28, 6:04 pm, Millisecond <[email protected]> wrote: > The query latency has been red on and off all morning, requests are > returning 500's and not counting as errors (saw another thread I was > going to reference about other people seeing this as well, but can't > find it now), but no alerts/status > updates:http://code.google.com/status/appengine/detail/datastore/2010/05/28#a... > > The only day marked as 'service disruption' was May 25th, but we've > thrown 75,000+ errors in the past week due to latency, not including > May 25th. > > Billing is missing and no word from Google on whether it's > intentional:http://groups.google.com/group/google-appengine/browse_thread/thread/... > > Would be great to hear about how this is all just a temporary thing, > what the problem is, and what Google's plan is to fix it. But, at the > moment, this feels like "normal operation" of AppEngine and nobody at > Google is concerned which really has me concerned. > > -C -- You received this message because you are subscribed to the Google Groups "Google App Engine" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/google-appengine?hl=en.
