hadoop-yarn-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "nemon lou (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (YARN-374) Job History Server doesn't show jobs which killed by ClientRMProtocol.forceKillApplication
Date Sat, 02 Feb 2013 08:20:12 GMT

     [ https://issues.apache.org/jira/browse/YARN-374?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

nemon lou updated YARN-374:
---------------------------

          Component/s: resourcemanager
                       client
    Affects Version/s: 2.0.1-alpha

The difference between bin/yarn and bin/mapred is that one use clientRMProtocol sending request
to RM and the other use MRClientProtocol sending request to AM.
                
> Job History Server doesn't show jobs which killed by ClientRMProtocol.forceKillApplication
> ------------------------------------------------------------------------------------------
>
>                 Key: YARN-374
>                 URL: https://issues.apache.org/jira/browse/YARN-374
>             Project: Hadoop YARN
>          Issue Type: Bug
>          Components: client, resourcemanager
>    Affects Versions: 2.0.1-alpha
>            Reporter: nemon lou
>
> After i kill a app by typing "bin/yarn rmadmin app -kill APP_ID",
> no job info is kept on JHS web page.
> However, when i kill a job by typing " bin/mapred  job -kill JOB_ID" ,
> i can see a killed job left on JHS.
> Some hive users are confused by that their jobs been killed but nothing left on JHS ,and
killed app's info on RM web page is not enough.(They kill job by clientRMProtocol)

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

Mime
View raw message