[FLINK-17493] Possible direct memory leak in cassandra sink

• Type: Sub-task
• Status: Open
• Priority: Minor
• Resolution: Unresolved
• Affects Version/s: 1.9.0, 1.10.0
• Component/s: Connectors / Cassandra
• Labels: auto-deprioritized-major
• Assignee: Unassigned
• Reporter: nobleyd
• Created: 01/May/20 13:30
• Updated: 24/Mar/22 08:59

Description

1. Cassandra Sink use direct memorys.
2. Start a standalone cluster(1 machines) for test.
3. After the cluster started, check the flink web-ui, and record the task manager's memory info. I mean the direct memory part info.
4. 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.
5. Stop the job, and the direct memory count is not decreased(using 'jmap -histo:live pid' to make the task manager gc).
6. Repeat serveral times, the direct memory count will be more and more.

Issue Links

• is duplicated by: FLINK-17494 Possible direct memory leak in cassandra sink