[
https://issues.apache.org/jira/browse/FLINK-9084?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17321599#comment-17321599
]
Flink Jira Bot commented on FLINK-9084:
---------------------------------------
This issue and all of its Sub-Tasks have not been updated for 180 days. So, it
has been labeled "stale-minor". If you are still affected by this bug or are
still interested in this issue, please give an update and remove the label. In
7 days the issue will be closed automatically.
> 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: Connectors / Cassandra
> Reporter: Jacob Park
> Assignee: Jacob Park
> Priority: Minor
> Labels: stale-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
(v8.3.4#803005)
