Notification of Master/Slave Datastore read-only period: July 21, 2014 starting at 16:00 US/Pacific

[Google App Engine Downtime Notify]

The Master/Slave Datastore will be read-only for up to 30 minutes starting at 16:00 US/Pacific on July 21, 2014. 

Applications using the High Replication Datastore to read or write data will not be impacted. 

The deprecated Master/Slave Datastore will be placed into read-only mode and Memcache will be flushed. It is recommended that critical portions of your application that depend on the Datastore should make use of the Capabilities API to detect and recover gracefully during read-only periods.

Documentation describing the capabilities API can be found here:

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

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

There will be no downtime for developers whose applications use High Replication Datastore. You can read more about High Replication here:

  http://googleappengine.blogspot.com/2011/01/announcing-high-replication-datastore.html

Here is more info about the deprecation of M/S:

  http://googleappengine.blogspot.com/2012/04/masterslave-datastore-thanks-for-all.html

To migrate your master/slave application to High Replication while preserving your application ID, you can use the migration tool that is provided in the Admin Console.Read more about this tool here:

  https://developers.google.com/appengine/docs/adminconsole/migration

[Google App Engine Downtime Notify]

This maintenance has been extended until 5:30pm PDT.

[Google App Engine Downtime Notify]

The maintenance period has finished.