[HIVE-5268] HiveServer2 accumulates orphaned OperationHandle objects when a client fails while executing query

• Type: Bug
• Status: Open
• Priority: Major
• Resolution: Unresolved
• Component/s: HiveServer2
• Assignee: Thiruvel Thirumoolan
• Reporter: Vaibhav Gumashta
• Created: 11/Sep/13 06:48
• Updated: 12/Nov/14 20:40

Description

When queries are executed against the HiveServer2 an OperationHandle object is stored in the OperationManager.handleToOperation HashMap. Currently its the duty of the JDBC client to explicitly close to cleanup the entry in the map. But if the client fails to close the statement then the OperationHandle object is never cleaned up and gets accumulated in the server.

This can potentially cause OOM on the server over time. This also can be used as a loophole by a malicious client to bring down the Hive server.

Issue Links

• is related to: HIVE-5296 Memory leak: OOM Error after multiple open/closed JDBC connections.
• relates to: HIVE-4501 HS2 memory leak - FileSystem objects in FileSystem.CACHE
• relates to: HIVE-5799 session/operation timeout for hiveserver2