I think the two options I gave you answer your question because deleting
a database it's not the same with deleting a document (deleting a
document just makes it unavailable, while deleting the database erase
physically the file from the harddisk). I know it's more a workaround
and it requires a bit of work, but it reclaims all the space used by the
deleted documents.
CGS
On 12/23/2011 09:56 PM, Chris Stockton wrote:
Hello,
On Fri, Dec 23, 2011 at 5:48 AM, CGS<[email protected]> wrote:
Hi,
Sorry to interfere with such a question, but why don't you work with a
buffer database? I mean, make a replica to another database which filters
out the deleted documents. In such way you can clean all your databases and
you use temporary some extra-space (only during the "cleaning" process).
Another idea would be to use two databases: one active and one inactive at
the given time. That means, you move the data from one to the other,
filtering out the deleted documents, and when it's over, you switch to the
newly constructed database, while the other gets emptied (deleted and
re-created). Just my 2c opinions.
CGS
Thanks everyone for the various feedback. Now the information I have
gathered is the disk utilization we are seeing is simply from the
deleted documents.
The question I have yet to see answered (perhaps because it simply
isn't possible) is how to reclaim this space?
-Chris