One note about the riak-erlang-client.
Timeouts will cause the client to disconnect.
So if you set a low timeout, it will get disconnected.
The behavior on disconnects can be configured with a couple of options
passed through at create time.
{ auto_reconnect, true } will reconnect if it gets di
Yes, I return connection to pool after query. Pool have 30 workers and most of
operations is single put. Ulimit in system is equal to 2048. We just started,
we store about 200-300 Mb of data on all cluster. We have about terabyte of
free space on server disks. Servers mostly stand by and waiting
I think the key may lie here ",{checkout,false,5000}"
Are you releasing your connections back to the pool? Is your throughput
greater than the system can handle due to limited connection pool sizes?
What is your ulimit set to (ulimit -n) ... maybe you're running out of
FD's?
-mox
On Wed,
I got nasty problem in production. We make connection pool with official erlang
pb client. Everything works fine. To organize pool we use hottub (we try
several,but that is simplest). Each connection used at least once in 3-5
minutes(production is not full loaded now).
After several days riak s
