[GitHub] [flink] StephanEwen removed a comment on issue #11196: [FLINK-16246][connector kinesis] Exclude AWS SDK MBean registry from Kinesis build

[GitBox <gi...@apache.org>]

StephanEwen removed a comment on issue #11196: [FLINK-16246][connector kinesis] Exclude AWS SDK MBean registry from Kinesis build
URL: https://github.com/apache/flink/pull/11196#issuecomment-591999051
 
 
   > If you have 2 separate jobs using the kinesis connector running on a single TM can it not still occur? Similarly if a plugin were to activate the sdk metrics (the S3 plugins have a dependency on aws-sdk-core and may be doing the same)?
   
   In the general case, depends how these "leak objects" are scoped.
   In this case I think it might work. The two jobs would be in different class loaders, load different copies of the AdminMBean class, and register multiple beans (it looks like there is specific code for collision of names and appending a number suffix in that case).  Deregistration would then deregister only the one from that classloader.

----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
users@infra.apache.org


With regards,
Apache Git Services