[
https://issues.apache.org/jira/browse/MAPREDUCE-5502?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jason Lowe updated MAPREDUCE-5502:
----------------------------------
Status: Open (was: Patch Available)
Thanks [~vrushalic] for posting a patch and sorry for the delay in reviewing it.
* It now always takes at least 10 seconds for jobs that have been submitted but
are not yet running to be killed. We should probably avoid trying to contact
the AM if the app is not in a terminal state and not running and just kill it
via YARN at that point.
* Nit: a static EnumSet might make the checking and maintenance of terminal
states a bit cleaner.
* Nit: it would be nice if unit tests could control the timeout used for the
kill, either via config or a package-private method, so we don't have to waste
10 seconds in the test
> History link in resource manager is broken for KILLED jobs
> ----------------------------------------------------------
>
> Key: MAPREDUCE-5502
> URL: https://issues.apache.org/jira/browse/MAPREDUCE-5502
> Project: Hadoop Map/Reduce
> Issue Type: Bug
> Components: resourcemanager
> Affects Versions: 2.0.5-alpha
> Reporter: Vrushali C
> Assignee: Vrushali C
> Labels: ui
> Attachments: patch_5502_2.txt, patch_5502_3_1.txt, patch_5502.txt
>
>
> History link in resource manager is broken for KILLED jobs.
> Seems to happen with jobs with State 'KILLED' and FinalStatus 'KILLED'. If
> the State is 'FINISHED' and FinalStatus is 'KILLED', then the "History" link
> is fine.
> It isn't easy to reproduce the problem since the time at which the app is
> killed determines the state it ends up in, which is hard to guess. these
> particular jobs seem to get a Diagnostics message of "Application killed by
> user." where as the other killed jobs get " Kill Job received from client
> job_1378766187901_0002
> Job received Kill while in RUNNING state. "
--
This message was sent by Atlassian JIRA
(v6.1#6144)
