Notification of upcoming master/slave maintenance period - Wednesday, February 29, 2012 - 4:00pm-5:30pm

[Ikai Lan]

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

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

Wednesday, February 29th, 4:00 PM - 5:30PM Pacific 

The master/slave datastore will be placed into a read-only period for the duration of this maintenance.

Below is the information we usually send out with these notifications. Check it out for more information about read-only periods, how to be notified of production events and how to migrate your application to High Replication.

- Ikai 

---------- 

The 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 

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:

http://code.google.com/appengine/docs/adminconsole/applicationsettings.html#Migrate_from_Master/Slave_to_High_Replication_Datastore

Developers can subscribe to the scheduled maintenance calendar using 

the following link: 

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