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

Posted to issues@flink.apache.org by "ASF GitHub Bot (Jira)" <ji...@apache.org> on 2024/12/03 07:57:00 UTC

[jira] [Updated] (FLINK-36835) Memory lease in flink-s3-fs module due to hadoop aws version 3.x

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

ASF GitHub Bot updated FLINK-36835:
-----------------------------------
    Labels: pull-request-available  (was: )

> Memory lease in flink-s3-fs module due to hadoop aws version 3.x
> ----------------------------------------------------------------
>
>                 Key: FLINK-36835
>                 URL: https://issues.apache.org/jira/browse/FLINK-36835
>             Project: Flink
>          Issue Type: Bug
>          Components: FileSystems
>    Affects Versions: 1.16.3, 1.17.2, 1.18.1, 1.20.0, 1.19.1
>            Reporter: JinxinTang
>            Priority: Major
>              Labels: pull-request-available
>             Fix For: 1.20.1
>
>
> From https://issues.apache.org/jira/browse/HADOOP-13028
> is introduced org.apache.hadoop.fs.s3a.S3AInstrumentation, it will be created every time org.apache.hadoop.fs.s3a.S3AFileSystem#initialize 
> and be registerd to static field meticsystem by org.apache.hadoop.fs.s3a.S3AInstrumentation#registerAsMetricsSource，but no one call 
> metricsSystem.unregisterSource(metricsSourceName); during runtime, it will cause memory lease when use filesystem plugin to write s3 storage



--
This message was sent by Atlassian Jira
(v8.20.10#820010)