[GitHub] [couchdb] chewbranca commented on issue #1998: Ioq per shard or user

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

chewbranca commented on issue #1998: Ioq per shard or user
URL: https://github.com/apache/couchdb/pull/1998#issuecomment-480955661
 
 
   > > IOQ Pid Eviction
   > 
   > For this topic, as well as evicting unused pids, don't we need some (configurable) global resource cap on the active pids to avoid resources being exhausted? I know inactive pids are likely tiny modulo resource leaks but they are not free right?
   
   @mikerhodes The model here basically switches to every active couch_file database shard pid having a dedicated IOQ2 process. As long as the primary database shard pid (or other clients) remain active, the IOQ2 pids remain active. Right now the global resource cap for active database shard pids is the `max_dbs_open` config value. This extends to the IOQ2 pid per shard, so total number of IOQ2 pids will be directly proportional to `max_dbs_open`. The `ioq_opener` monitors the active clients and will clear out IOQ2 pids upon all clients exiting so as to avoid leaving idle IOQ2 pids.

----------------------------------------------------------------
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


With regards,
Apache Git Services