[ https://issues.apache.org/jira/browse/HIVE-24636?focusedWorklogId=558506&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-558506 ]
ASF GitHub Bot logged work on HIVE-24636: ----------------------------------------- Author: ASF GitHub Bot Created on: 26/Feb/21 10:51 Start Date: 26/Feb/21 10:51 Worklog Time Spent: 10m Work Description: zmatyus commented on pull request #1923: URL: https://github.com/apache/hive/pull/1923#issuecomment-786571251 @pdbenitez91 : not sure what queries can make this the most visible. All I've seen was a report (Grafana screenshot) about increasing memory usage and a heap dump where the `factories` hashmap of `org.apache.commons.logging.LogFactory` holds on to thousands of class loaders, each of which retains some memory. I'm not sure either monitoring or head dump is an option with AWS. Seeing how this is about class loaders, you might experiment with queries that use Custom UDFs with lots of classes defined in their jar files... but I'm just guessing. ---------------------------------------------------------------- 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: us...@infra.apache.org Issue Time Tracking ------------------- Worklog Id: (was: 558506) Time Spent: 3h (was: 2h 50m) > Memory leak due to stacking UDFClassLoader in Apache Commons LogFactory > ----------------------------------------------------------------------- > > Key: HIVE-24636 > URL: https://issues.apache.org/jira/browse/HIVE-24636 > Project: Hive > Issue Type: Bug > Components: HiveServer2 > Affects Versions: 3.1.0 > Reporter: dohongdayi > Assignee: Zoltan Matyus > Priority: Major > Labels: pull-request-available > Fix For: 3.1.3, 3.2.0 > > Attachments: HIVE-24636.1.patch.txt > > Time Spent: 3h > Remaining Estimate: 0h > > Much the same asĀ [HIVE-7563|https://issues.apache.org/jira/browse/HIVE-7563], > after ClassLoader is closed in JavaUtils, it should be released by Apache > Commons LogFactory, or the ClassLoader can't be Garbage Collected, which > leads to memory leak, exactly our PROD met. -- This message was sent by Atlassian Jira (v8.3.4#803005)