Master/Slave 運用停止について


Google App Engine Master/Slave 運用停止について


Master/Slaveサーバ利用者に宛てて、Googleから正式に運用停止について連絡が来ていると思います。

メール一部引用

 Dear App Engine Developer

You are receiving this email because you are listed as an owner of a Google App Engine application that is configured to use the deprecated service Master/Slave Datastore, which will soon be shut down. Don’t worry though, this email gives clear instructions for what you need to do. Even if your application does not store data in Master/Slave Datastore, it is still configured to use Master/Slave Datastore, so please keep reading.

When we launched App Engine, Master/Slave Datastore was the only database service that applications could use to store data. Master/Slave Datastore had issues scaling with the size and complexity of applications running on App Engine, so we launched its successor, High Replication Datastore (HRD), in 2011. Since that launch HRD has proven to scale without issues.

One of our core goals with Google Cloud Platform is to provide customers with the best technologies to build their business, so when we saw that HRD was a more robust technology, we decided to make HRD the default database service. On April 4 2012 we announced the deprecation of Master/Slave Datastore -- our signal that three years from that date we would formally shut down the service.

That three years is upon us and, as mentioned above, one or more applications that you own (listed below) are running on Master/Slave Datastore. If you don’t take any action these applications will be shutdown on July 6, 2015 and will no longer serve traffic (users will see HTTP 404 responses).



メールによると、2015年7月6日午後12時(日本時間 2015年7月7日 午前4時)に Master/Slave が無効になり
アクセスしても 404 が返されるようになるようです。



 After the decommission, we will be providing a grace period of one month during which users can re-enable their applications in order to migrate to HRD. Throughout that month, re-enabled applications will be periodically disabled according to the following schedule:

On July 6, 2015, Master/Slave applications will be disabled at 12:00pm Pacific time. You will be able to re-enable these applications and you will be able to migrate to HRD.

On July 13, 2015, Master/Slave applications that were re-enabled will be disabled at 12:00pm Pacific time. You will be able to re-enable these applications and you will be able to migrate to HRD.

On July 20, 2015, Master/Slave applications that were re-enabled will be disabled at 12:00pm Pacific time. You will be able to re-enable these applications and you will be able to migrate to HRD.

Starting July 27, 2015, Master/Slave applications that were re-enabled will be disabled daily at 12:00pm Pacific time. You will be able to re-enable these applications and you will be able to migrate to HRD, however they’ll be disabled every business day at this time.

On August 3, 2015, you will no longer be able to re-enable your application, however you will still be able to migrate to HRD.

On August 10, 2015, your Master/Slave application will be permanently shut down and will no longer be accessible.

This means that after August 10, 2015 these applications will stop servicing requests and you will no longer have programmatic access to your data. If you no longer need your Master/Slave applications and associated data, no action is required. However, if you do need any of these applications we encourage you to migrate them to HRD immediately.

For more information please visit: Master-Slave Datastore Service Turndown.
If you have any questions about the Master/Slave Datastore decommission, you can reach us via the Master/Slave Datastore deprecation support form.

Regards,



7月6日に無効になっても、HRDへ移行する作業のため、1ヶ月間に限り再度有効にすることも出来るようですが
8月10日には、完全に運用が停止する模様です。

Master/Slaveサーバを利用していて、今後も使用継続されたい方は
HRDへの移行を7月6日までに行う必要があります。

(管理人、非常に多忙なため代理デプロイ等々お受け出来ません。すみません)



  • 最終更新:2015-03-25 14:55:40

このWIKIを編集するにはパスワード入力が必要です

認証パスワード