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 "Wangda Tan (Jira)" <ji...@apache.org> on 2020/10/01 19:06:00 UTC

[jira] [Commented] (MAPREDUCE-7298) Distcp doesn't close the job after the job is completed

    [ https://issues.apache.org/jira/browse/MAPREDUCE-7298?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17205770#comment-17205770 ] 

Wangda Tan commented on MAPREDUCE-7298:
---------------------------------------

+1, thanks for the patch.

> Distcp doesn't close the job after the job is completed
> -------------------------------------------------------
>
>                 Key: MAPREDUCE-7298
>                 URL: https://issues.apache.org/jira/browse/MAPREDUCE-7298
>             Project: Hadoop Map/Reduce
>          Issue Type: Task
>            Reporter: Aasha Medhi
>            Priority: Major
>         Attachments: MAPREDUCE-7298.01.patch, MAPREDUCE-7298.02.patch
>
>
> Distcp doesn't close the job after the job is completed. This leads to leaked Truststore Reloader Threads.
> The fix is to close the job once it is complete. job.close internally calls yarnClient.close(), which then calls timelineConnector.serviceStop() . This destroys the sslFactory cleaning up the ReloadingX509TrustManager.
> Without the patch for each distcp job, a new ReloadingX509TrustManager is created which creates a new thread. These threads are never killed and they remain like that till HS2 is restarted. With the close, the thread will be cleaned up once the job is completed.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

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