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/03/27 06:24:00 UTC

[jira] [Assigned] (FLINK-9083) Add async backpressure support to Cassandra Connector

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

Jacob Park reassigned FLINK-9083:
---------------------------------

    Assignee: Jacob Park

> Add async backpressure support to Cassandra Connector
> -----------------------------------------------------
>
>                 Key: FLINK-9083
>                 URL: https://issues.apache.org/jira/browse/FLINK-9083
>             Project: Flink
>          Issue Type: Improvement
>          Components: Cassandra Connector
>            Reporter: Jacob Park
>            Assignee: Jacob Park
>            Priority: Minor
>
> As the CassandraSinkBase derivatives utilize async writes, they do not block the task to introduce any backpressure.
> I am currently using a semaphore to provide backpressure support by blocking at a maximum concurrent requests limit like how DataStax's Spark Cassandra Connector functions: [https://github.com/datastax/spark-cassandra-connector/blob/v2.0.7/spark-cassandra-connector/src/main/scala/com/datastax/spark/connector/writer/AsyncExecutor.scala#L18]
> This improvement has greatly improved the fault-tolerance of our Cassandra Sink Connector implementation on Apache Flink in production. I would like to contribute this feature back upstream.



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