Reminder: Scheduled Maintenance, February 17th, 5:00 PM Pacific Time

[App Engine Team]

Reminder: there will be a scheduled maintenance period for App Engine
next Wednesday, February 17th, at 5:00 PM Pacific Time for up to one
hour. The datastore will be in read-only mode during this time period;
all datastore writes and transactions will throw an exception.

During this scheduled maintenance, memcache will also be disabled.
Calls to the memcache API will not throw exceptions but will instead
return False for set() calls and None for get() calls (just like any
other cache miss). In addition, memcache API calls will return
immediately during this period, without any additional latency.

It is recommended that critical portions of your application which
depend on datastore writes are modified to gracefully degrade. Links
to our documentation with code samples are below:

Python: http://code.google.com/appengine/docs/python/howto/maintenance.html
Java: http://code.google.com/appengine/docs/java/howto/maintenance.html

You can subscribe to our maintenance calendar here:

Google Calendar:
http://www.google.com/calendar/embed?src=4chlpo92ci2f54c2u21shbjk9o%40group.calendar.google.com&ctz=America/Los_Angeles
iCal: http://www.google.com/calendar/ical/4chlpo92ci2f54c2u21shbjk9o%40group.calendar.google.com/public/basic.ics

[App Engine Team]

This is just a reminder that scheduled maintenance will be happening
tomorrow, February 17th between 5pm and 6pm. Please plan accordingly.

On Feb 9, 2:37 pm, App Engine Team <appengine.nore...@gmail.com>
wrote:

> Reminder: there will be a scheduled maintenance period for App Engine
> next Wednesday, February 17th, at 5:00 PM Pacific Time for up to one
> hour. The datastore will be in read-only mode during this time period;
> all datastore writes and transactions will throw an exception.
>
> During this scheduled maintenance, memcache will also be disabled.
> Calls to the memcache API will not throw exceptions but will instead
> return False for set() calls and None for get() calls (just like any
> other cache miss). In addition, memcache API calls will return
> immediately during this period, without any additional latency.
>
> It is recommended that critical portions of your application which
> depend on datastore writes are modified to gracefully degrade. Links
> to our documentation with code samples are below:
>
> Python:http://code.google.com/appengine/docs/python/howto/maintenance.html
> Java:http://code.google.com/appengine/docs/java/howto/maintenance.html
>
> You can subscribe to our maintenance calendar here:
>

> Google Calendar:http://www.google.com/calendar/embed?src=4chlpo92ci2f54c2u21shbjk9o%4...
> iCal:http://www.google.com/calendar/ical/4chlpo92ci2f54c2u21shbjk9o%40grou...

[App Engine Team]

This is an update on the scheduled maintenance. Maintenance will begin
at 6:15pm and end around 7:15pm Pacific Time. During this time,
applications will be placed into read-only mode.

We apologize for any inconvenience from the delay.

On Feb 16, 4:33 pm, App Engine Team <appengine.nore...@gmail.com>

[App Engine Team]

Yet another update: maintenance mode has begun around 5:45pm and will
end around 6:15pm. The datastore has been placed into read-only mode.

We apologize for any confusion we may have caused.

On Feb 17, 5:37 pm, App Engine Team <appengine.nore...@gmail.com>

[App Engine Team]

Maintenance was completed at 6:20pm. It is now possible to write to
the datastore again.

On Feb 17, 5:47 pm, App Engine Team <appengine.nore...@gmail.com>

[App Engine Team]

While the maintenance and read-only period are over, there are ongoing
performance issues with App Engine specifically related to datastore,
app deployments and cron tasks. Note that Cron tasks are only delayed
and will be executed as we catch up from the backlog during the
outage. For App deployments, there is a known workaround that
should work for most developers:

1. Deploy your application as a new version. Please do not constantly
attempt to redeploy your app. Your app is already in the queue even if
the deploy script times out.
2. Validate that the new version is active using the <version>.latest
URL
3. Use the Admin Console to switch the active or default application
to this version

Thank you for your patience. We are working to improve the
performance issues as quickly as possible.

On Feb 17, 6:30 pm, App Engine Team <appengine.nore...@gmail.com>

[App Engine Team]

As of 9:25 PST the performance problems have cleared up and the
lingerings issues have been resolved.

On Feb 17, 7:58 pm, App Engine Team <appengine.nore...@gmail.com>