You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@sentry.apache.org by "Prasad Mujumdar (JIRA)" <ji...@apache.org> on 2015/04/22 09:49:58 UTC
[jira] [Commented] (SENTRY-705) Possible memory leak of
HiveAuthzBinding.authzBindingMap
[ https://issues.apache.org/jira/browse/SENTRY-705?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14506602#comment-14506602 ]
Prasad Mujumdar commented on SENTRY-705:
----------------------------------------
Likely same issue as SENTRY-699
> Possible memory leak of HiveAuthzBinding.authzBindingMap
> --------------------------------------------------------
>
> Key: SENTRY-705
> URL: https://issues.apache.org/jira/browse/SENTRY-705
> Project: Sentry
> Issue Type: Bug
> Reporter: Binglin Chang
>
> We are using hive0.13 with sentry, version cdh5.2.0, noticed that hiveserver uses lot of memory and doesn't get freed.
> Memory profiling showed that there are lots(millions) of HiveConf and HiveAuthzConf instances hold by HiveAuthzBinding.authzBindingMap
> Look at the code, related call order:
> Driver.compile
> HiveAuthzBindingHook.preAnalyze
> HiveAuthzBindingHook.postAnalyze
> hiveAuthzBinding.set
> Driver.execute
> HiveAuthzBindingPreExecHook.run
> hiveAuthzBinding.clear
> Between Driver.compile and Driver.execute, there are too many logic(which sentry can not control), not sure hiveAuthzBinding.clear is guaranteed to be called
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)