sentry-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hadoop QA (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (SENTRY-705) Possible memory leak of HiveAuthzBinding.authzBindingMap
Date Sat, 09 May 2015 16:51:00 GMT

    [ https://issues.apache.org/jira/browse/SENTRY-705?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14536759#comment-14536759
] 

Hadoop QA commented on SENTRY-705:
----------------------------------

Here are the results of testing the latest attachment
https://issues.apache.org/jira/secure/attachment/12731719/SENTRY-705.001.patch against master.

{color:red}Overall:{color} -1 due to an error

{color:red}ERROR:{color} failed to apply patch (exit code 1):
The patch does not appear to apply with p0, p1, or p2



Console output: https://builds.apache.org/job/PreCommit-SENTRY-Build/583/console

This message is automatically generated.

> Possible memory leak of HiveAuthzBinding.authzBindingMap
> --------------------------------------------------------
>
>                 Key: SENTRY-705
>                 URL: https://issues.apache.org/jira/browse/SENTRY-705
>             Project: Sentry
>          Issue Type: Bug
>    Affects Versions: 1.4.0
>            Reporter: Binglin Chang
>         Attachments: SENTRY-705.001.patch
>
>
> 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)

Mime
View raw message