[
https://issues.apache.org/jira/browse/FLINK-26793?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17512513#comment-17512513
]
Etienne Chauchot commented on FLINK-26793:
------------------------------------------
[~bumblebee] copying what I wrote on the ML:
On a regular pipeline such as
_org.apache.flink.streaming.connectors.cassandra.example.CassandraPojoSinkExample_
with a parallelism of 4 you will have 4 _CassandraPojoSink_ with for each, one
{_}MappingManager{_}, one Cassandra _Cluster_ and one Cassandra _Session._ This
is perfectly right as the sinks in production could reside on different
taskManagers on different machines.
You can test it yourself by running in debug mode _CassandraPojoSinkExample_
locally and count the number of these objects in your local JVM. Don't forget
to start a local Cassandra cluster (with docker for example) listening on
127.0.0.1:9042 and create the keyspace and table described in
{_}CassandraPojoSinkExample{_}.
Could you give more details on your particular issue ?
> 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)
