couchdb-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Robert Newson <>
Subject Re: Database too large for partition
Date Thu, 11 Jul 2013 19:13:41 GMT
" but you need space equal to the content of the database to do a compaction."

That's not true. You need space equal to the "disk_size" value from
GET /dbname. The only time your statement would be true is if you
compacted a database that you had just compacted and had made no
changes to. Compacting it again will just write the whole thing out
again. Obviously this worse case is also the case where there's no
point compacting anyway.


On 11 July 2013 20:00, Tim Tisdall <> wrote:
> You could delete the generated views in /var/lib/couchdb/.your_database/
> and recover a little extra space.  There could also be a partially done
> compaction in /var/lib/couchdb/
> The longer term solution is to do compactions... but you need space equal
> to the content of the database to do a compaction.
> On Thu, Jul 11, 2013 at 2:56 PM, Matthias Eck <>wrote:
>> Hello,
>> I have a CouchDB database that is on a 1TB partition on Amazon EC2.
>> Unfortunately the database now filled the whole partition and 1TB is the
>> size limit on Amazon EC2, so I cannot copy it to a larger partition.
>> 1. I would like to get the database running again. Are there any files that
>> I can safely delete to save some immediate space so CouchDB will run again?
>> 2. Any suggestions to solve this problem longer-term? Is it possible to
>> have a database spanning multiple partitions?
>> Thanks,
>> Matthias

View raw message