Re: Solve Busy pool at Cassandra side

2018-05-13 Thread Jonathan Haddad
This error comes from com.datastax.driver.core.HostConnectionPool#enqueue, which is the client side pool. Cassandra can handle more requests, the application needs to be fixed. As per the java docs: /** * Indicates that a connection pool has run out of available connections. * * This

Solve Busy pool at Cassandra side

2018-05-13 Thread onmstester onmstester
Hi, I'm getting "Pool is Busy (limit is 256)", while connecting to a single node cassandra cluster. The whole client side application is a 3rd-party lib which i can't change it's source and its session builder is not using any PoolingOptions. Is there any config on cassandra side that could