Mailing-List: contact user-help@couchdb.apache.org; run by ezmlm
Precedence: bulk
Reply-To: user@couchdb.apache.org
Received-SPF: pass (nike.apache.org: domain of sebastiancohnen@googlemail.com
 designates 209.85.161.52 as permitted sender)
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=googlemail.com; s=gamma;
        h=content-type:mime-version:subject:from:in-reply-to:date
         :content-transfer-encoding:message-id:references:to:x-mailer;
        b=V0pC5Rsqf0J69kwyHL/RmfMLC41rYec9Jw2r7p90fPeq0EX4YsKJpsOstvuWtdeDRq
         eFUv+BBe9cH+nzDAk4by/ma+pgRNAoGy2QfivgXNoS4Zb+IjP2srSz6lJFgcSbcm4kCP
         HW/bsgKE0T79bGQXKLz3rfm+IllU6SG4fjB+E=
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Apple Message framework v1078)
Subject: Re: Query about chef compaction - why would it fail silently?
From: Sebastian Cohnen <sebastiancohnen@googlemail.com>
In-Reply-To: <5BAC863F-488C-468F-B7CF-423309BD5B6D@headshift.com>
Date: Fri, 14 May 2010 12:28:36 +0200
Content-Transfer-Encoding: quoted-printable
Message-Id: <69065A34-C7FD-4A69-8604-29B9BA2FA7DD@googlemail.com>
References: <3B7C8162-71B0-4F60-BB6F-F5D857143A7A@headshift.com>
 <C449A456-AE05-4757-B59D-7020BA91CAA5@googlemail.com>
 <5BAC863F-488C-468F-B7CF-423309BD5B6D@headshift.com>
To: user@couchdb.apache.org

hmm,

can you check if compaction is running? GET http://localhost:5984/chef/ =
should tell you with the "compact_running"-field. Also check the =
_active_tasks endpoint for running compaction tasks: GET =
http://localhost:5984/_active_tasks.

If compaction is not running, look for suspicious error messages in the =
log file (maybe on debug-loglevel).

Please be aware that compacting 9GB can take some time...


On 14.05.2010, at 11:10, Chris Adams wrote:

> Thanks the reply Sebastian!
>=20
> I've since extended the drive to allow for a compaction, but calling =
_compact still doesn't seem to start the compaction process:
>=20
> I've gisted the same system stats again below, it it helps:
>=20
> http://gist.github.com/400920
>=20
> Any other ideas?
>=20
> C
>=20
> On 14 May 2010, at 09:40, Sebastian Cohnen wrote:
>=20
>> I hope couchdb is not at /dev/mapper/system-var :) you need some free =
space, because couch is copying all the latest, non-conflicting =
documents over to a new file and afterwards swaps out the old database =
file with the newly created one.
>>=20
>> On 14.05.2010, at 10:00, Chris Adams wrote:
>>=20
>>> Hi there,
>>>=20
>>> I'm a little confused by the behaviour of couchdb's compact command, =
and I suspect the solution is really quite simple, but I'm still new to =
couchdb, so please excuse the noobish question:
>>>=20
>>> I'm trying to compact a 5.6gb couchdb database that's been generated =
by chef, using this command:
>>>=20
>>> curl -X POST http://localhost:5984/chef/_compact
>>>=20
>>> However, when I check the status back, couch doesn't seem to be =
compacting:
>>>=20
>>> curl -X GET http://localhost:5984/chef/
>>>=20
>>> I'm following the insturctions here - =
http://wiki.apache.org/couchdb/Compaction=20
>>>=20
>>> Why might it not start compacting when I call the compact command =
like this? =20
>>>=20
>>> The VM that's running the couchdb database is almost at capacity =
disk space wise, and I'm using couchdb version 0.10.0 (I've gisted this =
info here http://gist.github.com/400920, and the output from the compact =
commands here )
>>>=20
>>> Thanks!
>>>=20
>>> Chris Adams
>>>=20
>>>=20
>>>=20
>>>=20
>>>=20
>>>=20
>>=20
>=20