Notification of upcoming Master/Slave maintenance period - Thursday 3 January 2013, 5pm US/Pacific

[Amy Unruh]

(If your application is already using the High Replication datastore, you can ignore this email.)

We are scheduling a maintenance period that will impact applications running on the deprecated master/slave datastore:

Thursday 3 January 2013, 5pm US/Pacific

The master/slave datastore will be placed into a read-only period for the duration of this maintenance, though we are targeting a shorter read-only period.

Below is the information we usually send out with these notifications.

It has more information about read-only periods, how to be notified of production events and how to migrate your application to High Replication.

 -Amy

----------

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

Developers can subscribe to the scheduled maintenance calendar using the following link:

  https://www.google.com/calendar/b/0/embed?src=4chlpo92ci2f5...@group.calendar.google.com&ctz=America/Los_Angeles&gsessionid=OK

[Amy Unruh]

The announcement below neglected to specify an end time for the maintenance.  The maintenance period will be from 5pm-7pm US/Pacific, Thursday 3 January 2013.

 -Amy

[Amy Unruh]

Reminder: there is an upcoming maintenance period that will 

impact applications running on the deprecated master/slave datastore: 

Thursday 3 January 2013, 5pm-7pm, US/Pacific.

[Amy Unruh]

This maintenance period will start very shortly; I'll post again when it is actually underway.

(There is currently a known issue with some M/S apps, for which a fix is in progress, and those affected will need to wait until the maintenance period finishes to check those apps).

[Amy Unruh]

This maintenance period has now started.  I'll post again when it has finished.

[Amy Unruh]

The maintenance period has finished.