You are viewing a plain text version of this content. The canonical link for it is here.
Posted to mapreduce-issues@hadoop.apache.org by "Jason Lowe (JIRA)" <ji...@apache.org> on 2016/02/01 17:02:39 UTC
[jira] [Commented] (MAPREDUCE-6618) YarnClientProtocolProvider
leaking the YarnClient thread.
[ https://issues.apache.org/jira/browse/MAPREDUCE-6618?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15126449#comment-15126449 ]
Jason Lowe commented on MAPREDUCE-6618:
---------------------------------------
+1 lgtm. Committing this.
> YarnClientProtocolProvider leaking the YarnClient thread.
> ----------------------------------------------------------
>
> Key: MAPREDUCE-6618
> URL: https://issues.apache.org/jira/browse/MAPREDUCE-6618
> Project: Hadoop Map/Reduce
> Issue Type: Bug
> Reporter: Xuan Gong
> Assignee: Xuan Gong
> Attachments: MAPREDUCE-6618.1.patch, MAPREDUCE-6618.2.patch, MAPREDUCE-6618.3.patch, MAPREDUCE-6618.4.patch, MAPREDUCE-6618.5.patch, MAPREDUCE-6618.6.patch
>
>
> YarnClientProtocolProvider creates YarnRunner which includes ResourceMgrDelegate. In ResourceMgrDelegate, we would initiate and start yarnclient. The yarnClient thread would be leaked due to
> {code}
> @Override
> public void close(ClientProtocol clientProtocol) throws IOException {
> // nothing to do
> }
> {code} in YarnClientProtocolProvider
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)