[GitHub] [couchdb-nano] BrodaUa commented on issue #267: Support over 1k changes feed listeners

[GitBox <gi...@apache.org>]

BrodaUa commented on issue #267:
URL: https://github.com/apache/couchdb-nano/issues/267#issuecomment-843869947


   @glynnbird Thank you for the extensive answer. As of now, it is anticipated to have up to 10k users. 
   Indeed, maxSockets can be a bottle neck. I missed that cause official **nano** docs says: _By default, the Node.js HTTP global agent has a_ **infinite** _number of active connections that can run simultaneously_.
   I tried to modify the HttpAgent with maxSockets=32k, but now I get an issue with CouchDB: *No DB shards could be opened*. 
   I have the next CouchDB custom config
   ```
   [cluster]
   q=4
   [httpd]
   enable_cors=true
   [cors]
   origins=*
   [chttpd]
   server_options=[{backlog, 512}, {acceptor_pool_size, 16}, {max, 32768}]
   [couchdb]
   max_dbs_open=32768
   ```
   
   I run the db as a docker image https://hub.docker.com/_/couchdb/ via docker-compose, also tried to tune the system file descriptors 
   ```
   services:
     couchdb:
       image: couchdb:3.1
       ulimits: 
         nofile: 128000
   ```
   
   but it has no effect, still the same shards issue. 
   Although, when I deacrease the maxSockets=128, there is **no** shards issue, Do you have any idea why maxSockets causes it?


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

For queries about this service, please contact Infrastructure at:
users@infra.apache.org