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

Posted to issues@flink.apache.org by "Etienne Chauchot (Jira)" <ji...@apache.org> on 2022/04/01 15:54:00 UTC

[jira] [Commented] (FLINK-26793) Flink Cassandra connector performance issue

    [ https://issues.apache.org/jira/browse/FLINK-26793?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17515978#comment-17515978 ] 

Etienne Chauchot commented on FLINK-26793:
------------------------------------------

[~bumblebee] The only thing I can think of is that _CassandraPojoSink_ was recreated for example after a failure/recovery. In that case it would recreate the _MappingManager_ and thus loose the prepared statements stored in it. Do you see anything in the Flink logs ?

> Flink Cassandra connector performance issue 
> --------------------------------------------
>
>                 Key: FLINK-26793
>                 URL: https://issues.apache.org/jira/browse/FLINK-26793
>             Project: Flink
>          Issue Type: Improvement
>          Components: Connectors / Cassandra
>    Affects Versions: 1.14.4
>            Reporter: Jay Ghiya
>            Assignee: Etienne Chauchot
>            Priority: Major
>
> A warning is observed during long runs of flink job stating “Insertions into scylla might be suffering. Expect performance problems unless this is resolved.”
> Upon initial analysis - “flink cassandra connector is not keeping instance of mapping manager that is used to convert a pojo to cassandra row. Ideally the mapping manager should have the same life time as cluster and session objects which are also created once when the driver is initialized”
> Reference: https://stackoverflow.com/questions/59203418/cassandra-java-driver-warning



--
This message was sent by Atlassian Jira
(v8.20.1#820001)