Uploaded image for project: 'James Server'
  1. James Server
  2. JAMES-2318

Expose Cassandra PoolingOptions::setMaxQueueSize

    Details

    • Type: Improvement
    • Status: Open
    • Priority: Major
    • Resolution: Unresolved
    • Affects Version/s: None
    • Fix Version/s: None
    • Component/s: cassandra

      Description

      The logs contains some entries like:

      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)))
      

      We would like to expose Cassandra driver PoolingOptions::setMaxQueueSize, in order to see the impact on such configuration parameter on, dropped Cassandra requests.

      This can be done by:

      • Adding more configuration options in *ResilientClusterProvider*::readPoolingOptions
      • You will need to add documentation in `/src/site/xdoc/server/config-cassandra.xml`

      If you want to do it, reach us in the chat (https://gitter.im/apache/james-project)! We will give you detailed guidelines.

        Attachments

          Activity

            People

            • Assignee:
              Unassigned
              Reporter:
              BTellier Tellier Benoit
            • Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

              Dates

              • Created:
                Updated: