[ https://issues.apache.org/jira/browse/YARN-1382?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15075139#comment-15075139 ]
Hudson commented on YARN-1382: ------------------------------ FAILURE: Integrated in Hadoop-trunk-Commit #9038 (See [https://builds.apache.org/job/Hadoop-trunk-Commit/9038/]) YARN-1382. Remove unusableRMNodesConcurrentSet (never used) in (junping_du: rev 223ce323bb81463ec5c5ac7316738370d4a47366) * hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-resourcemanager/src/main/java/org/apache/hadoop/yarn/server/resourcemanager/NodesListManager.java * hadoop-yarn-project/CHANGES.txt > Remove unusableRMNodesConcurrentSet (never used) in NodeListManager to get > rid of memory leak > --------------------------------------------------------------------------------------------- > > Key: YARN-1382 > URL: https://issues.apache.org/jira/browse/YARN-1382 > Project: Hadoop YARN > Issue Type: Bug > Components: resourcemanager > Affects Versions: 2.2.0, 2.7.1, 2.6.2 > Reporter: Alejandro Abdelnur > Assignee: Rohith Sharma K S > Fix For: 2.8.0 > > Attachments: 0001-YARN-1382.patch, 0002-YARN-1382.patch, > 0003-YARN-1382.patch > > > If a node is in the unusable nodes set (unusableRMNodesConcurrentSet) and > never comes back, the node will be there forever. > While the leak is not big, it gets aggravated if the NM addresses are > configured with ephemeral ports as when the nodes come back they come back as > new. > Some related details in YARN-1343 -- This message was sent by Atlassian JIRA (v6.3.4#6332)