[
https://issues.apache.org/jira/browse/YARN-5438?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15398376#comment-15398376
]
Hudson commented on YARN-5438:
------------------------------
SUCCESS: Integrated in Hadoop-trunk-Commit #10172 (See
[https://builds.apache.org/job/Hadoop-trunk-Commit/10172/])
YARN-5438. TimelineClientImpl leaking FileSystem Instances causing Long (jlowe:
rev a1890c32c52fed69ec09efad0fccf49ed8c2e21e)
*
hadoop-yarn-project/hadoop-yarn/hadoop-yarn-common/src/main/java/org/apache/hadoop/yarn/client/api/impl/FileSystemTimelineWriter.java
> TimelineClientImpl leaking FileSystem Instances causing Long running services
> like HiverServer2 daemon going OOM
> ----------------------------------------------------------------------------------------------------------------
>
> Key: YARN-5438
> URL: https://issues.apache.org/jira/browse/YARN-5438
> Project: Hadoop YARN
> Issue Type: Bug
> Components: timelineserver
> Affects Versions: 2.8.0, 2.7.3
> Reporter: Karam Singh
> Assignee: Rohith Sharma K S
> Fix For: 2.8.0
>
> Attachments: YARN-5438.0.patch
>
>
> TimelineClientImpl leaking FileSystem Instances causing Long running services
> like HiverServer2 daemon going OOM
> In org.apache.hadoop.yarn.client.api.impl.TimelineClientImpl,
> FileSystem.newInstance is invoked and is not closed. Causing over time
> Filesystem instances getting accumulated in long runninh Client (like
> Hiveserver2), finally causing them to OOM
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
