Thanks for the quick response.
We're just about to start some testing on an Erlang 16-based CouchDB
environment so we'll see what result we get with this (but this could take a
few weeks).
Re: compaction, we have the following configured for all databases and views to
be compacted:
-----------------------------------
"compactions": {
"_default": "[{db_fragmentation, \"50%\"}, {view_fragmentation,
\"50%\"}]"
-----------------------------------
Re: logging, I've attached a log but I'm not seeing anything relevant in it.
Note that, at the moment, only 'error'-level messages are logged. I am somewhat
reluctant to enable 'info'-level logging as this can create large log files
very quickly. I will do if necessary though. Could I set logging on a
particular module only, one that is specifically relevant to the process that
causes the problem?
Something I forgot to say in my initial report is that the databases on this
server replicate continuously to databases on another server, thus provided us
with a real time backup. The backup server is not affected by this problem,
only the live server. don't know if this is relevant.
---------------------------------------------------------------------------------------
This email has been scanned for email related threats and delivered safely by
Mimecast.
For more information please visit http://www.mimecast.com
---------------------------------------------------------------------------------------
