One common gotcha with limits.conf is that couchdb su's to the couchdb user and /etc/pam.d/su in debian/ubuntu defaults to *not* respecting limits.conf, you need to enable it.
B. On 4 Oct 2013, at 02:38, Ramkrishna Kulkarni <[email protected]> wrote: > I'm initiating over 100 one shot replications to as many servers from a > central server. When I do this, central CouchDB slows down a lot (Requests > to DBs time out) even though enough system resources are available. I do > not see more than 600 connections (netstat -an | grep -i established | wc > -l) being opened at the time of replication. My config looks something like > this: > > [couchdb] > max_dbs_open = 10000 > > [httpd] > max_connections = 10240 > > [replicator] > worker_processes = 30 > http_connections = 30 > > /etc/security/limits.conf > * - nofile 65535 > > ulimit -n > 65535 > > This is CouchDB 1.4.x on Ubuntu 12.04 32-bit, 8-cores, 6GB RAM. > > I was hoping to see at least 3000 connections - 30 per replication. Is > there some other config I'm missing? > > Thanks, > Ram
signature.asc
Description: Message signed with OpenPGP using GPGMail
