You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@pig.apache.org by "Rohini Palaniswamy (JIRA)" <ji...@apache.org> on 2014/04/02 21:18:15 UTC

[jira] [Commented] (PIG-3853) Pig does not kill all the jobs during shutdown for hadoop2

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

Rohini Palaniswamy commented on PIG-3853:
-----------------------------------------

RunningJob would also refer to jobs that are in UNDEFINED state as well. If AM was not started yet, the RunningJob will constructed with information from RM. Did you encounter a situation where that was not the case?

> Pig does not kill all the jobs during shutdown for hadoop2
> ----------------------------------------------------------
>
>                 Key: PIG-3853
>                 URL: https://issues.apache.org/jira/browse/PIG-3853
>             Project: Pig
>          Issue Type: Bug
>            Reporter: Aniket Mokashi
>            Assignee: Aniket Mokashi
>
> Current code -
> {code}
> for (Job job : jc.getRunningJobs()) {
>                     RunningJob runningJob = getJob(job.getJobClient(), job.getAssignedJobID());
>                     if (runningJob!=null) {
>                         runningJob.killJob();
>                         log.info("Job " + job.getAssignedJobID() + " killed");
>                     }
>                 }
> {code}
> is not sufficient for killing all the submitted jobs. It does not kill the jobs that are submitted to the cluster but are in UNDEFINED state (with appid but no app-master).



--
This message was sent by Atlassian JIRA
(v6.2#6252)