Perhaps try triggering the compaction directly from the API with curl?
http://docs.couchdb.org/en/1.6.1/api/database/compact.html
Adam
> On Jun 30, 2015, at 3:45 AM, Travis Downs wrote:
>
> I ran compaction via the button in _utils. I did notice that when I
> clicked the button, the spinner in
Ah, this one I think I can explain. The compactor in CouchDB 1.x writes
documents directly to the new file in batches. If the IDs of those documents
are essentially random in nature, the compacted file can end up with a lot of
wasted space. By contrast, if the document IDs in the _changes feed a
I ran compaction via the button in _utils. I did notice that when I
clicked the button, the spinner in the UI never stops, but I did check
that compact_running was "false" for the DB in question - so I assumed
it finished. I suppose some issue with _utils could instead mean it
never started? Is the
