[
https://issues.apache.org/jira/browse/HADOOP-10357?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13908571#comment-13908571
]
Larry McCay commented on HADOOP-10357:
--------------------------------------
Hi Daryn - Yes, the UGI is created and disposed of per connection. I believe
the trouble comes from the static UgiInstrumentation field within the UGI.
Which is why we end up with at least 1 UgiInstrumentation instance per
connection that was made and dropped. I guess it should be characterized as a
UgiInstrumentation leak from within UGI? Anyway, I will be following up with a
VisualVM screen capture showing that accumulation of UgiInstrumentation
instances as well as a test program that can be used to reproduce it.
> Memory Leak in UserGroupInformation.doAs for JDBC Connection to Hive
> --------------------------------------------------------------------
>
> Key: HADOOP-10357
> URL: https://issues.apache.org/jira/browse/HADOOP-10357
> Project: Hadoop Common
> Issue Type: Bug
> Components: security
> Affects Versions: 1.2.0
> Reporter: Larry McCay
>
> When using UGI.doAs in order to make a connection there appears to be a
> memory leak involving the UGI that is used for the doAs and the UGI held by
> TUGIAssumingTransport.
> When using this approach to establishing a JDBC connection in an environment
> that will serve many users and requests client side eventually runs out of
> memory.
--
This message was sent by Atlassian JIRA
(v6.1.5#6160)
