maxPoolSize

Hi

I am getting the following error with the .net client "Pool is full, timeouting"

Here is my socketPool setting

There are 3 couchbase servers running in a cluster

We have 7 servers hosting the same site and get about 10 000 requests per second on average on the site.

The couchbase servers has about 6k ops per second(not all from the site in question) and between 4k-6k connections(not all from the site in question)

The couchbase servers CPU usage is between 20% and 40%

It is obviously a pool size problem. What is the maximum that the maxPoolSize can be and what is the maximum connections that the servers will be able to handle?

thanks

1 Answer

« Back to question.

Hi ockert -

The connection pool size is set at a min of 10 and a max of 20 as a default, meaning that the pool will start at 10 connections and grow as needed up to 20 connections. You can set the min anywhere between 1 and whatever your max is set to, but that will definitely cause client time out issues if you constrain the pool size too much; due to resource contention. Likewise, too many connections and you will wasting resources - your better off making incremental adjustments and measuring the impact.

Oh yes, and the max number of client connections for a node in a cluster is 10k.