You are viewing a plain text version of this content. The canonical link for it is here.
Posted to yarn-issues@hadoop.apache.org by "Jason Lowe (JIRA)" <ji...@apache.org> on 2013/12/17 17:31:08 UTC
[jira] [Updated] (YARN-1145) Potential file handle leak in
aggregated logs web ui
[ https://issues.apache.org/jira/browse/YARN-1145?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jason Lowe updated YARN-1145:
-----------------------------
Fix Version/s: 0.23.11
Thanks, Rohith! I committed this to branch-0.23 as well.
> Potential file handle leak in aggregated logs web ui
> ----------------------------------------------------
>
> Key: YARN-1145
> URL: https://issues.apache.org/jira/browse/YARN-1145
> Project: Hadoop YARN
> Issue Type: Bug
> Affects Versions: 2.0.5-alpha, 0.23.9, 2.1.1-beta
> Reporter: Rohith
> Assignee: Rohith
> Fix For: 2.4.0, 0.23.11
>
> Attachments: MAPREDUCE-5486.patch, YARN-1145.1.patch, YARN-1145.2.patch, YARN-1145.3.patch, YARN-1145.4.patch, YARN-1145.patch
>
>
> Any problem in getting aggregated logs for rendering on web ui, then LogReader is not closed.
> Now, it reader is not closed which causing many connections in close_wait state.
> hadoopuser@hadoopuser:> jps
> *27909* JobHistoryServer
> DataNode port is 50010. When greped with DataNode port, many connections are in CLOSE_WAIT from JHS.
> hadoopuser@hadoopuser:> netstat -tanlp |grep 50010
> tcp 0 0 10.18.40.48:50010 0.0.0.0:* LISTEN 21453/java
> tcp 1 0 10.18.40.48:20596 10.18.40.48:50010 CLOSE_WAIT *27909*/java
> tcp 1 0 10.18.40.48:19667 10.18.40.152:50010 CLOSE_WAIT *27909*/java
> tcp 1 0 10.18.40.48:20593 10.18.40.48:50010 CLOSE_WAIT *27909*/java
> tcp 1 0 10.18.40.48:12290 10.18.40.48:50010 CLOSE_WAIT *27909*/java
> tcp 1 0 10.18.40.48:19662 10.18.40.152:50010 CLOSE_WAIT *27909*/java
--
This message was sent by Atlassian JIRA
(v6.1.4#6159)