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

["Jay Ghiya (Jira)" <ji...@apache.org>]

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

Jay Ghiya edited comment on FLINK-26793 at 4/5/22 5:04 PM:
-----------------------------------------------------------

Hi [~echauchot] - Regardin "query is not prepared ..." -> No this is not observed. So it is possible that restarts would have happened. we have seen that quite frequent in our aks dev environment. I might not be able to check previous logs as of now in terms of checkpoints as we run lyft flink operator. That cluster would not be present since quite some time now. But i can start one more reliability run to confirm the same. Will keep you posted.i should have update by friday end of day. Hope this helps :) 


was (Author: bumblebee):
Hi [~echauchot] - Regardin "query is not prepared ..." -> No this is not observed. So it is possible that restarts would have happened. we have seen that quite frequent in our aks dev environment. I might not be able to check previous logs as of now in terms of checkpoints as we run lyft flink operator. But i can start one more reliability run to confirm the same. Will keep you posted.i should have update by friday end of day. Hope this helps :) 

> 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)