You are viewing a plain text version of this content. The canonical link for it is here.

Posted to common-issues@hadoop.apache.org by "ZanderXu (Jira)" <ji...@apache.org> on 2023/02/08 03:47:00 UTC

[jira] [Created] (HADOOP-18624) Leaked calls may cause ObserverNameNode OOM.

ZanderXu created HADOOP-18624:
---------------------------------

             Summary: Leaked calls may cause ObserverNameNode OOM.
                 Key: HADOOP-18624
                 URL: https://issues.apache.org/jira/browse/HADOOP-18624
             Project: Hadoop Common
          Issue Type: Bug
            Reporter: ZanderXu
            Assignee: ZanderXu


Leaked calls may cause ObserverNameNode OOM.

 

During Observer Namenode tailing edits from JournalNode, it will cancel slow request with an interruptException if there are a majority of successful responses. 

There is a bug in Client.java, it will not clean the interrupted call from the calls. The leaked calls may cause ObserverNameNode OOM.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

---------------------------------------------------------------------
To unsubscribe, e-mail: common-issues-unsubscribe@hadoop.apache.org
For additional commands, e-mail: common-issues-help@hadoop.apache.org