You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@flink.apache.org by "Zhu Zhu (Jira)" <ji...@apache.org> on 2020/08/10 12:37:00 UTC
[jira] [Updated] (FLINK-16246) Exclude "SdkMBeanRegistrySupport"
from dynamically loaded AWS connectors
[ https://issues.apache.org/jira/browse/FLINK-16246?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Zhu Zhu updated FLINK-16246:
----------------------------
Fix Version/s: (was: 1.10.2)
1.10.3
1.11.2
> Exclude "SdkMBeanRegistrySupport" from dynamically loaded AWS connectors
> ------------------------------------------------------------------------
>
> Key: FLINK-16246
> URL: https://issues.apache.org/jira/browse/FLINK-16246
> Project: Flink
> Issue Type: Bug
> Components: Connectors / Kinesis
> Reporter: Stephan Ewen
> Assignee: Stephan Ewen
> Priority: Major
> Labels: pull-request-available
> Fix For: 1.12.0, 1.11.2, 1.10.3
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> The AWS SDK always registers a {{MetricAdminMBean}} at the JMX MBean Server.
> This allows users to turn on / off more detailed metrics via the JMX admin interface.
> However, this registered bean keeps the user code classloader alive and thus causes a class leak.
> Excluding the {{com.amazonaws.jmx.SdkMBeanRegistrySupport}} class from the connectors disables the default registration thus preventing the class leak. It should only disable that JMX metric admin interface and still allow users to manually configure/activate metrics for the AWS SDK.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)