[
https://issues.apache.org/jira/browse/YARN-5401?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15384529#comment-15384529
]
Jason Lowe commented on YARN-5401:
----------------------------------
Yes, if an application framework provides a kill command then that should be
preferred over the yarn kill approach. The MapReduce framework kill will
automatically fallback to the yarn kill if the application master is
unresponsive or if the job fails to enter the killed state within a
configurable amount of time (controlled via
yarn.app.mapreduce.am.hard-kill-timeout-ms).
> 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]
