You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@flink.apache.org by "Jacob Park (JIRA)" <ji...@apache.org> on 2018/10/01 00:16:00 UTC

[jira] [Updated] (FLINK-9084) Upgrade cassandra-driver-core to 3.6.0 to introduce BusyPoolException retries to Cassandra Connector

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

Jacob Park updated FLINK-9084:
------------------------------
    Summary: Upgrade cassandra-driver-core to 3.6.0 to introduce BusyPoolException retries to Cassandra Connector  (was: Upgrade cassandra-driver-core to 3.4.0 to introduce BusyPoolException retries to Cassandra Connector)

> Upgrade cassandra-driver-core to 3.6.0 to introduce BusyPoolException retries to Cassandra Connector
> ----------------------------------------------------------------------------------------------------
>
>                 Key: FLINK-9084
>                 URL: https://issues.apache.org/jira/browse/FLINK-9084
>             Project: Flink
>          Issue Type: Improvement
>          Components: Cassandra Connector
>            Reporter: Jacob Park
>            Assignee: Jacob Park
>            Priority: Minor
>
> As per [https://datastax-oss.atlassian.net/browse/SPARKC-503,] that exception will be thrown by executeAsync() since at least 3.1.4 as executeAsync() is fully async, so it throws that exception if the driver-side pool is busy. 
> This improvement has greatly improved the peek throughput of our Cassandra Sink Connector. It also allowed us to get all the benefits of the latest driver version.
> I would like to contribute this feature back upstream.



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