ChoiByungHo created ZEPPELIN-6260:
-------------------------------------
Summary: Memory leak in WebSocket watcher connections -
watcherSockets not cleaned up on connection close
Key: ZEPPELIN-6260
URL: https://issues.apache.org/jira/browse/ZEPPELIN-6260
Project: Zeppelin
Issue Type: Bug
Reporter: ChoiByungHo
Contents:
When a WebSocket connection is switched to watcher mode via the WATCHER
message, it gets added to the watcherSockets queue in ConnectionManager.
However, when the connection is closed, the socket is never removed from this
queue, causing a memory
leak.
Steps to reproduce:
1. Open a WebSocket connection to Zeppelin
2. Send a WATCHER message to switch to watcher mode
3. Close the connection
4. The connection remains in watcherSockets queue indefinitely
Impact:
- Memory usage increases over time as closed watcher connections accumulate
- Can lead to OutOfMemoryError in long-running Zeppelin servers
Fix:
Add removeWatcherConnection() method to ConnectionManager and call it during
connection cleanup in NotebookServer.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
