You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@flink.apache.org by "nobleyd (Jira)" <ji...@apache.org> on 2020/05/14 13:57:00 UTC

[jira] [Updated] (FLINK-17493) Possible direct memory leak in cassandra sink

     [ https://issues.apache.org/jira/browse/FLINK-17493?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

nobleyd updated FLINK-17493:
----------------------------
    Affects Version/s:     (was: 1.9.3)
                       1.9.0

> Possible direct memory leak in cassandra sink
> ---------------------------------------------
>
>                 Key: FLINK-17493
>                 URL: https://issues.apache.org/jira/browse/FLINK-17493
>             Project: Flink
>          Issue Type: Bug
>          Components: Connectors / Cassandra
>    Affects Versions: 1.9.0, 1.10.0
>            Reporter: nobleyd
>            Priority: Major
>
> # Cassandra Sink use direct memorys.
>  # Start a standalone cluster(1 machines) for test.
>  # After the cluster started, check the flink web-ui, and record the task manager's memory info. I mean the direct memory part info.
>  # Start a job which read from kafka and write to cassandra using the cassandra sink, and you can see that the direct memory count in 'Outside JVM' part go up.
>  # Stop the job, and the direct memory count is not decreased(using 'jmap -histo:live pid' to make the task manager gc).
>  # Repeat serveral times, the direct memory count will be more and more.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)