Re: 100% CPU on only a single node because of couchjs processes

I've finally managed to narrow this down to a reproducible set of scripts and have created a GH issue: https://github.com/apache/couchdb/issues/1063 The summary is that I believe there is a resource leak in CouchDB when you abort continuous listening on the _global_changes database. Fortunately,

Re: Automatic Compaction of _global_changes

Great, glad to hear it. And yes, each compaction daemon only watches the shard files that are hosted on the local node. Cheers, Adam > On Dec 11, 2017, at 2:37 PM, > wrote: > > Hi Adam, > > Thanks for the clarification. I updated

RE: Automatic Compaction of _global_changes

Hi Adam, Thanks for the clarification. I updated my config and it worked! In the below example, I had included the compaction rules for all four nodes in the config for one node. In retrospect, this probably doesn't make sense since I think the compaction daemon would only see its local

Re: 100% CPU on only a single node because of couchjs processes

I just found this, it may solve the problem by removing it. It is a script that starts the crypto mining program as user couchdb. [image: Inline images 1] On 11 December 2017 at 15:04, Sinan Gabel wrote: > > > I have now checked it, and it is as you @Robert perceived, a

Re: 100% CPU on only a single node because of couchjs processes

I have now checked it, and it is as you @Robert perceived, a crypto mining program. It is a program "fs-manager" with config.json as given below that is restarted every 3 hours or so (8:41, 11:41 etc.) unless it keeps running. I updated couchdb to latest version and changed all admin passwords