Details
-
Improvement
-
Status: Closed
-
Minor
-
Resolution: Fixed
-
None
-
None
Description
In case of exception in SQLOperation, operational log does not get cleared up. This causes gradual build up of HushableRandomAccessFileAppender causing HS2 to OOM after some time.
Allocation tree
Prod instance mem
Each HushableRandomAccessFileAppender holds internal ref to RandomAccessFileAppender which holds a 256 KB bytebuffer, causing the mem leak.
Related ticket: HIVE-18820
Attachments
Attachments
Issue Links
- causes
-
HIVE-25970 Missing messages in HS2 operation logs
- Closed
- is a parent of
-
HIVE-24590 Operation Logging still leaks the log4j Appenders
- Closed
- is related to
-
HIVE-17128 Operation Logging leaks file descriptors as the log4j Appender is never closed
- Closed
-
HIVE-24569 LLAP daemon leaks file descriptors/log4j appenders
- Closed
- relates to
-
HIVE-22127 Query Routing logging appender is leaking resources of RandomAccessFileManager.
- Open