213f385348
Before, a really lagged cluster might not get its final report for a deleted container database sent to its corresponding account database. In such a case, the container database file would be permanently deleted while still leaving the container listed in the account database, never to be updated since the actual container database file was gone. The only way to fix such the situation before was to recreate and redelete the container. Now, the container database file will not be permanently deleted until it has sent its final report successfully to its corresponding account database. Change-Id: I1f42202455e7ecb0533b84ce7f45fcc7b98aeaa3
Swift ----- A distributed object store that was originally developed as the basis for Rackspace's Cloud Files. To build documentation run `python setup.py build_sphinx`, and then browse to /doc/build/html/index.html. The best place to get started is the "SAIO - Swift All In One", which will walk you through setting up a development cluster of Swift in a VM. For more information, visit us at http://launchpad.net/swift, or come hang out on our IRC channel, #openstack on freenode. -- Swift Development Team