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

Stamatis Zampetakis commented on HIVE-24590:
--------------------------------------------

I assume the reason of why there is still a leak is the same with HIVE-24569, 
meaning that cleanup is performed with Operation#cleanupOperationLog so one 
appender is closed but then another thread comes and attempts to write to the 
same file thus creating an additional appender that will never be closed.

This also explains why the content of the respective log file has only one 
line. During the {{cleanupOperationLog}}, {{OperationLogCleaner}} is called so 
the full operation log file will be deleted but then if somebody else tries to 
write to it (e.g., TezClient) the file will be recreated leading to the leak. 

> Operation Logging still leaks the log4j Appenders
> -------------------------------------------------
>
>                 Key: HIVE-24590
>                 URL: https://issues.apache.org/jira/browse/HIVE-24590
>             Project: Hive
>          Issue Type: Bug
>          Components: Logging
>            Reporter: Eugene Chung
>            Assignee: Stamatis Zampetakis
>            Priority: Major
>         Attachments: Screen Shot 2021-01-06 at 18.42.05.png, Screen Shot 
> 2021-01-06 at 18.42.24.png, Screen Shot 2021-01-06 at 18.42.55.png
>
>
> I'm using Hive 3.1.2 with options below.
>  * hive.server2.logging.operation.enabled=true
>  * hive.server2.logging.operation.level=VERBOSE
>  * hive.async.log.enabled=false
> I already know the ticket, https://issues.apache.org/jira/browse/HIVE-17128 
> but HS2 still leaks log4j RandomAccessFileManager.
> !Screen Shot 2021-01-06 at 18.42.05.png|width=756,height=197!
> I checked the operation log file which is not closed/deleted properly.
> !Screen Shot 2021-01-06 at 18.42.24.png|width=603,height=272!
> Then there's the log,
> {code:java}
> client.TezClient: Shutting down Tez Session, sessionName= ....{code}
> !Screen Shot 2021-01-06 at 18.42.55.png|width=1372,height=26!



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

Reply via email to