[jira] [Updated] (JAMES-2318) Expose Cassandra PoolingOptions::setMaxQueueSize

["Tellier Benoit (JIRA)" <se...@james.apache.org>]

     [ https://issues.apache.org/jira/browse/JAMES-2318?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Tellier Benoit updated JAMES-2318:
----------------------------------
    Labels: easyfix feature newbie  (was: easy-fix feature newbie)

> Expose Cassandra PoolingOptions::setMaxQueueSize
> ------------------------------------------------
>
>                 Key: JAMES-2318
>                 URL: https://issues.apache.org/jira/browse/JAMES-2318
>             Project: James Server
>          Issue Type: Improvement
>          Components: cassandra
>            Reporter: Tellier Benoit
>            Priority: Major
>              Labels: easyfix, feature, newbie
>
> The logs contains some entries like:
> {code:java}
> java.util.concurrent.CompletionException: com.datastax.driver.core.exceptions.NoHostAvailableException: All host(s) tried for query failed (tried: /172.17.0.1:9042 (com.datastax.driver.core.exceptions.BusyPoolException: [/172.17.0.1] Pool is busy (no available connection and the queue has reached its max size 256)))
> {code}
> We would like to expose Cassandra driver PoolingOptions::setMaxQueueSize, in order to see the impact on such configuration parameter on, dropped Cassandra requests.
> If you want to do it, reach us in the chat (https://gitter.im/apache/james-project)! We will give you detailed guidelines.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

---------------------------------------------------------------------
To unsubscribe, e-mail: server-dev-unsubscribe@james.apache.org
For additional commands, e-mail: server-dev-help@james.apache.org