メールの内容を大雑把でいいので翻訳してください
Google App Engineから、本日以下のようなメールが届きました。
英語が苦手で、内容がどうしてもよく分かりません…
(GAEはTwitterのbot制作のため、使い方サイトを見ながら何とか登録したという状態です)
大雑把でいいので、どのような内容なのか翻訳していただけないでしょうか？
最後の段落の1行目で「できるだけ早くアプリケーションを移行することをお勧めします。」といったことが書かれていて、とても重要なことなのかと不安になっています。
よろしくお願いいたします。
以下メール本文-----------------------------------------
We’ve noticed that you are running at least one application configured to use the Master/Slave (M/S) datastore. This application configuration was officially deprecated on April 4, 2012, in accordance with our deprecation policy, in favor of the more reliable High Replication Datastore (HRD). HRD uses the Paxos algorithm to serve your application out of multiple datacenters, meaning better redundancy in the face of datacenter issues, more consistent datastore performance, and no planned downtime.
When we deprecated the M/S datastore, we introduced a migration tool that allows you to easily migrate all your datastore and blobstore data to a new HRD application. Migrating your application will not require you to change your application’s URL, whether it serves from appspot.com or a custom domin. Please note that even if your application does not store any data in the datastore, it will still benefit from the automated datacenter failover that is only available to HRD applications.
Before migrating your application, you should read about the differences between M/S and HRD, and understand how the consistency policy for HRD might affect the queries in your application.
All HRD applications that have billing enabled are covered by App Engine’s 99.95% uptime SLA. Along with the substantial reliability improvements, many new App Engine features are only being made available to HRD applications, including the Python 2.7 language option, Full Text Search (FTS), and Page Speed integration.
We strongly encourage you to migrate your applications as soon as possible. If you have technical questions about HRD or the migration process, you can post them to Stack Overflow. Any general migration discussions can be posted to our Google Group.
