[
https://issues.apache.org/jira/browse/FLINK-26793?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17518255#comment-17518255
]
Jay Ghiya commented on FLINK-26793:
-----------------------------------
absolutely. [~echauchot] makes sense. we have also started the run again today.
To answer your first question we have not observed "query is not prepared" .
for the second question -> we do not have logs for our previous run now. We
are rerunning. [~chesnay]-> Hi. so we did not observe back pressure in terms of
operator metrics. But we wanted to check whether the implementation (the task)
is creating only instance of mapping manager and that [~echauchot] confirmed.
so we are good on that.
> 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)
