Our Couchdb server (1.5.0, browserID plugin) was slow in responding to views and _all_dbs (getting a attachment was working reasonably fast).
I was looking at the terminal couchdb was started in and I noticed that beam.smp was using 209% cpu power (7 cpu's available) while normally it rarely gets above 50%. After a minute or two I noticed a lot of error's in the console's. (pasted the first few to pastebin: ttp://pastebin.com/3syn8P3a) Right in between the crash notifications I noticed a lot of these: [Tue, 12 Nov 2013 14:20:02 GMT] [info] [<0.18180.38>] Index shutdown by monitor notice for db: At least once per database in couchdb. Eventually I had to stop the couchdb process (Ctrl-C in the terminal). After checking the ulimits (wouldn't be the first time we hit "open files") I restarted couchdb and everything returned to normal. Does anyone have an idea of what happend here? -- The ulimits of the server: # ulimit -a core file size (blocks, -c) 0 data seg size (kbytes, -d) unlimited scheduling priority (-e) 0 file size (blocks, -f) unlimited pending signals (-i) 124507 max locked memory (kbytes, -l) 64 max memory size (kbytes, -m) unlimited open files (-n) 124507 pipe size (512 bytes, -p) 8 POSIX message queues (bytes, -q) 819200 real-time priority (-r) 0 stack size (kbytes, -s) 8192 cpu time (seconds, -t) unlimited max user processes (-u) 124507 virtual memory (kbytes, -v) unlimited file locks (-x) unlimited -- Met vriendelijke groet, Pieter van der Eems Interactive Blueprints
