[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)
[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: Attachment: image-2020-05-14-21-58-59-152.png > 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 > Attachments: image-2020-05-14-21-58-59-152.png > > > # 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)
[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 ] Flink Jira Bot updated FLINK-17493: --- Labels: stale-major (was: ) > 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 > Labels: stale-major > Attachments: image-2020-05-14-21-58-59-152.png > > > # 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)
[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 ] Flink Jira Bot updated FLINK-17493: --- Labels: auto-deprioritized-major (was: stale-major) > 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 > Labels: auto-deprioritized-major > Attachments: image-2020-05-14-21-58-59-152.png > > > # 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)
[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 ] Flink Jira Bot updated FLINK-17493: --- Priority: Minor (was: Major) > 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: Minor > Labels: auto-deprioritized-major > Attachments: image-2020-05-14-21-58-59-152.png > > > # 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)
[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 ] Martijn Visser updated FLINK-17493: --- Parent: FLINK-26820 Issue Type: Sub-task (was: Bug) > Possible direct memory leak in cassandra sink > - > > Key: FLINK-17493 > URL: https://issues.apache.org/jira/browse/FLINK-17493 > Project: Flink > Issue Type: Sub-task > Components: Connectors / Cassandra >Affects Versions: 1.9.0, 1.10.0 >Reporter: nobleyd >Priority: Minor > Labels: auto-deprioritized-major > Attachments: image-2020-05-14-21-58-59-152.png > > > # 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.20.1#820001)
