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

["Etienne Chauchot (Jira)" <ji...@apache.org>]

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

Etienne Chauchot edited comment on FLINK-26793 at 6/13/22 9:04 AM:
-------------------------------------------------------------------

[~arvid], I went through the code as promised: flink code cannot influence the cassandra cluster behavior as described above (there is no timeout options available in the driver) just the cassandra cluster conf option mentioned above. So, I propose to submit a PR to add my comments above to the javadocs of the sinks and outputformats.


was (Author: echauchot):
[~arvid], I went through the code as promised: flink code cannot influence the cassandra cluster behavior as described above (there is no timeout options available in the driver) just the cassandra cluster conf option mentioned above. So, I propose to submit a PR to add this documentation to the sinks and outputformats.

> 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
>              Labels: documentation
>         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)