[
https://issues.apache.org/jira/browse/MAPREDUCE-7298?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17202859#comment-17202859
]
Aasha Medhi commented on MAPREDUCE-7298:
----------------------------------------
1. UT added
2. Description added to Jira
[~shashikant] Job will get cleaned only if its a blocking call to run. If its a
non blocking call, I don't see a way to get the job reference. How will that
get cleaned up?
> 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
>
>
> 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-unsubscr...@hadoop.apache.org
For additional commands, e-mail: mapreduce-issues-h...@hadoop.apache.org
