2010 6 11 09:56 AM 1567次查看
App Engine applications you own affected by unapplied writes说的是5月25日的一次outage，我的gaejava应用因为大量写入，部分数据没有及时同步，于是变成了unapplied writes。
During the day of May 25th, 2010, Google App Engine experienced a serving outage that lasted approximately 50 minutes. In the minutes leading up to the outage, we received a number of writes from your application that we were unable to replicate to the secondary Datastore. This caused the secondary Datastore to be slightly out of sync when we began serving traffic as part of the outage recovery process. We call these type of writes “unapplied writes.” Rest assured, unapplied writes do not impact the transactional consistency and have not corrupted your application data.
The follow applications you own have unapplied writes:
During the recovery of the failed data center, we were able to produce a log of the unapplied writes that occurred during the outage period. As a service to you, these unapplied writes are now available from within your application’s to make it easy for you to re-integrate them. We have also developed a number of tools and example on how to do so. If you are interested in better understanding this logged data and how you can work with it, please visit the Unapplied Writes FAQ: http://code.google.com/appengine/kb/unappliedwrites.html
Additionally, if you have any follow up questions please reply to this email. We can also work with you to re-integrate or delete your entities in batch as you see fit for your application.
No action is required on your part; you can choose to ignore these writes if you choose. We're making these writes available to you because we want you to know that whenever possible, we take every step we can to recover any data, complete or incomplete, that you attempt to store on App Engine.
We apologize for any inconvenience this may have caused you and thank you for your continued support of Google App Engine.
The App Engine team
最后，GAE blog也提到了此事，并且说数据库延迟的问题应该会在下周解决，届时GAE blog会发文公告。