[
https://issues.apache.org/jira/browse/FLINK-9084?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jacob Park updated FLINK-9084:
------------------------------
Description:
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.
was:
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.
> Upgrade cassandra-driver-core to 3.4.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
> 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)
