[
https://issues.apache.org/jira/browse/FLINK-26793?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17527329#comment-17527329
]
Arvid Heise commented on FLINK-26793:
-------------------------------------
Just to double-check: Can we optimize anything on Flink side to lower the
performance drop on restart? For me, it looks like there is nothing and we
should just include the information about the timeout on the Cassandra
documentation page (maybe even in the Javadocs).
> 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
> Attachments: Capture d’écran de 2022-04-14 16-34-59.png, Capture
> d’écran de 2022-04-14 16-35-07.png, Capture d’écran de 2022-04-14
> 16-35-30.png, jobmanager_log.txt, taskmanager_127.0.1.1_33251-af56fa_log
>
>
> 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.7#820007)
