The app is on MS, Python 2.5. I am okay with occasional scheduled read-only period for maintenance, as migrating the database is not straight-forward for this app, which is metadata driven (data-store entity names are based on key-ids and are referenced within other metadata.. views, actions, work-flows, etc.,. I am not sure if the migration tool will retain the same key-ids)
I am just puzzled why this specific instance alone is continuing to have these issues for an extended period of time, while my other MS - Python 2.5 apps (including another with identical setup) seem to work fine. Why can't this app work fine too.. is what I wonder. Thanks for tip though, T. -Raj On Thu, Dec 29, 2011 at 6:19 PM, timh <[email protected]> wrote: > Are you on MS or HR (I am assuming python) > > If on MS historically you could find yourself in a bit of appengine > infrastructure that is having a bad hair day and raised latencies can > turn into slow import times and then DEE's and instances not starting. > > The system status will look fine as their monitoring isn't looking at > every machine but the service as a whole. > > T > > -- > 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/-/jqI2A2cyJnAJ. > 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. > -- 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.
