Bug #6221
Updated by Tom Clegg almost 9 years ago
By design, Data Manager deletes unneeded blocks by sending "trash lists" does not issue delete commands yet to the keepstore Keep servers. Currently, Data Manager computes lists of trashable blocks, but doesn't send them to the keepstore servers. Before this can be implemented and deployed: * trash_worker.go must respect the @never_delete@ flag, and this must be tested. When this is set, it should log a message (including the locator of the block being deleted) instead of deleting the file. * data manager must send its trash lists to keep servers * data manager must have _at least_ one comprehensive integration test covering a miniature version of normal operation: ** bring up api, keepstore, and keepproxy services ** store some collections ** run data manager ** wait for all keepstores to finish working their trash and pull lists ** delete some of the collections ** reduce replication on some of the collections ** run data manager again ** bring up at least one more keepstore ** turn off one keepstore ** run data manager again ** wait for all keepstores to finish working their trash and pull lists ** make sure all non-garbage blocks are stored at the correct replication level, and in their optimal positions