Hacker News new | past | comments | ask | show | jobs | submit login

I wish CouchDB would implement internal compaction. I'd love to use CouchDB and Elastic Search with the CouchDB River plugin. This would give me a nice REST infrastructure with a schemaless store (couchDB) and the ability to do complex queries in real time (elastic search).

Sadly my data is too write/update-heavy and just keeps on growing and growing. This means that I'll have to use compaction if I don't want to run out of space sooner or later. Starting compaction will kill performance over several hours and depending on the amount of written data might not even be able to finish :(




We are working on auto compaction. The Couchbase alpha already supports it. This should help, but it will help even more on a cluster as each shard can be compacted independently.


does "auto compaction" mean that the compaction process is just automatically triggered?


Yes, but only when certain configurable conditions are met (fragmentation level, time period). There's some user level documentation in the default.ini config file:

https://github.com/couchbase/couchdb/blob/preview/etc/couchd...


ok, that would still lead to a situation where my server crawls to a halt for hours and might never finish if I don't basically take it offline :(




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: