Hey everyone,
(If your application is already using High Replication datastore, you can ignore this email. To tell if a currently deployed application is using High Replication, go to your application's admin console and look at the dropdown menu in the top left hand corner of the page. If the selected application shows "YOUR_APP_ID [High Replication]" (where YOUR_APP_ID = your application ID), you are already running on High Replication and can ignore this message.)
We're planning an upcoming scheduled maintenance period in September:
Wednesday, November 30th, 5:30 PM - 6:30PM Pacific
For everyone that's not currently on high replication datastore, we'll be releasing a self-service migration tool very soon. This self service migration tool minimizes the amount of read-only downtime and creates an alias pointing the current master/slave application ID to the new, high replication application ID, effectively allowing developers to preserve the app ID. Please sign up for early access here:
Below is the standard information we usually send out with these notifications. Check it out for more information about read-only periods or how to be notified of production events.
- Ikai
----------
The 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:
There will be no downtime for developers whose applications use High
Replication Datastore. You can read more about High Replication here:
Developers can subscribe to the scheduled maintenance calendar using
the following link: