Return-Path: X-Original-To: apmail-sentry-commits-archive@minotaur.apache.org Delivered-To: apmail-sentry-commits-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id C02B817DF0 for ; Sat, 9 May 2015 16:48:01 +0000 (UTC) Received: (qmail 34617 invoked by uid 500); 9 May 2015 16:48:01 -0000 Delivered-To: apmail-sentry-commits-archive@sentry.apache.org Received: (qmail 34567 invoked by uid 500); 9 May 2015 16:48:01 -0000 Mailing-List: contact commits-help@sentry.incubator.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@sentry.incubator.apache.org Delivered-To: mailing list commits@sentry.incubator.apache.org Received: (qmail 34558 invoked by uid 99); 9 May 2015 16:48:01 -0000 Received: from Unknown (HELO spamd1-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Sat, 09 May 2015 16:48:01 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd1-us-west.apache.org (ASF Mail Server at spamd1-us-west.apache.org) with ESMTP id 48AC4C39EF for ; Sat, 9 May 2015 16:48:01 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd1-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: 0.97 X-Spam-Level: X-Spam-Status: No, score=0.97 tagged_above=-999 required=6.31 tests=[KAM_LAZY_DOMAIN_SECURITY=1, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, T_RP_MATCHES_RCVD=-0.01] autolearn=disabled Received: from mx1-us-east.apache.org ([10.40.0.8]) by localhost (spamd1-us-west.apache.org [10.40.0.7]) (amavisd-new, port 10024) with ESMTP id bjYTM95P7fre for ; Sat, 9 May 2015 16:48:00 +0000 (UTC) Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by mx1-us-east.apache.org (ASF Mail Server at mx1-us-east.apache.org) with SMTP id 63706453EF for ; Sat, 9 May 2015 16:48:00 +0000 (UTC) Received: (qmail 34509 invoked by uid 99); 9 May 2015 16:48:00 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Sat, 09 May 2015 16:48:00 +0000 Date: Sat, 9 May 2015 16:47:59 +0000 (UTC) From: "Binglin Chang (JIRA)" To: commits@sentry.incubator.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Updated] (SENTRY-705) Possible memory leak of HiveAuthzBinding.authzBindingMap MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/SENTRY-705?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Binglin Chang updated SENTRY-705: --------------------------------- Attachment: SENTRY-705.001.patch > 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)