Hi,
You could try something like (I tried to cleanup the code from other
stuff in the gist-editor, so it might not compile directly) the
following for your scheduling:
https://gist.github.com/burmanm/230c306f88c69c62dfe737994444fc01
That should prevent pool getting full, instead using the old blocking
behavior for your code. Add your own twist of backpressure handling to
the code obviously.
- Micke
On 08/23/2017 09:40 PM, Avi Levi wrote:
Hi ,
I need to execute large amount (millions) of select queries. but I am
getting BusyPoolExcption how can I avoid that ? I tried to configure
the pooling options but couldn't see that it had any impact
Any advice ?
|Failed to execute query SELECT * FROM my_table WHERE id = 'some_uuid'
AND x >= 1503501104 AND y < 1503501224;
com.datastax.driver.core.exceptions.NoHostAvailableException: All
host(s) tried for query failed (tried: localhost/0:0:0:0:0:0:0:1:9042
(com.datastax.driver.core.exceptions.BusyPoolException:
[localhost/0:0:0:0:0:0:0:1] Pool is busy (no available connection and
the queue has reached its max size 256)))|
---------------------------------------------------------------------
To unsubscribe, e-mail: user-unsubscr...@cassandra.apache.org
For additional commands, e-mail: user-h...@cassandra.apache.org
