csantanapr commented on issue #3071: delete old activations doesn't free disk 
space
URL: 
https://github.com/apache/incubator-openwhisk/issues/3071#issuecomment-349843880
 
 
   Even after doing a purge follow by a compact, disk size will not shrink as 
docs are never deleted.
   
   
[_purge](http://docs.couchdb.org/en/2.1.1/api/database/misc.html?highlight=purge#post--db-_purge)
   ```
   Purging documents does not remove the space used by them on disk. To reclaim 
disk space, you should run a database compact (see /db/_compact), and compact 
views (see /db/_compact/design-doc).
   ```
   with compat you are removing old revisions, so not a complete delete
   
[_compat](http://docs.couchdb.org/en/2.1.1/api/database/compact.html#db-compact)
   ```
   Writes a new, optimised, version of the database file, removing any unused 
sections from the new version during write. Because a new file is temporarily 
created for this purpose, you may require up to twice the current storage space 
of the specified database in order for the compaction routine to complete.
   Removes old revisions of documents from the database, up to the per-database 
limit specified by the _revs_limit database parameter.
   ```
   
   If you want to really delete docs, for example old activations that you 
don't care about them after certain period you would need to use a new db, and 
replicate docs you really want to keep.
   
   There are a few blogs around the web that talk about this: 
https://eclipsesource.com/blogs/2015/04/20/how-to-finally-delete-documents-in-couchdb/
   
   For whisk db holding docs for entities like actions, then purge and compat 
are more effective, deleting old history.
   

----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
[email protected]


With regards,
Apache Git Services

Reply via email to