hadoop-mapreduce-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Rohith Sharma K S (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (MAPREDUCE-5882) org.apache.hadoop.mapreduce.tools.CLI doesn't close cluster on job submit.
Date Thu, 27 Oct 2016 10:58:58 GMT

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

Rohith Sharma K S commented on MAPREDUCE-5882:
----------------------------------------------

I believe it is intentional since at any point of time JobClient can get some information.
In CLI, however mapred client get exited. So would you explain what is the impact?

> org.apache.hadoop.mapreduce.tools.CLI doesn't close cluster on job submit.
> --------------------------------------------------------------------------
>
>                 Key: MAPREDUCE-5882
>                 URL: https://issues.apache.org/jira/browse/MAPREDUCE-5882
>             Project: Hadoop Map/Reduce
>          Issue Type: Bug
>    Affects Versions: 2.3.0
>            Reporter: Vladimir Ozerov
>            Priority: Critical
>
> When job is submitted through CLI class, Job connects to the cluster. However, cluster
is never closed in this case and ClientProtocolProvider.close() is never invoked. 
> In all other cases Cluster is gracefully closed explicitly in finally block.
> This can be easily resolved e.g. by wrapping call to job.submit() in try-finally block:
> try {
>     job.submit();
> }
> finally {
>     Cluster jobCluster = job.getCluster();
>     if (jobCluster != null)
>         jobCluster.close();
> }



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

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


Mime
View raw message