[
https://issues.apache.org/jira/browse/YARN-5401?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15384516#comment-15384516
]
Nikhil Mulley commented on YARN-5401:
-------------------------------------
So, should apps always use app specific methods to kill their jobs but never
use yarn kill unless really necessary. (like always use kill(TERM) unless kill
-9 becomes necessary)
> yarn application kill does not let mapreduce jobs show up in jobhistory
> -----------------------------------------------------------------------
>
> Key: YARN-5401
> URL: https://issues.apache.org/jira/browse/YARN-5401
> Project: Hadoop YARN
> Issue Type: Bug
> Components: yarn
> Environment: centos 6.6
> apache hadoop 2.6.4
> Reporter: Nikhil Mulley
>
> Hi,
> Its been found in our cluster running apache hadoop 2.6.4, that while the
> mapreduce jobs that are killed with 'hadoop job -kill' command do end up have
> the job and its counters to jobhistory server but when 'yarn application
> -kill' is used on mapreduce application, job does not show up in jobhistory
> server interface.
> Is this intentional? If so, any particular reasons?
> It would be better to have mapreduce application history reported on
> jobhistory irrespective of whether kill is performed using yarn application
> cli or hadoop job cli.
> thanks,
> Nikhil
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
