We're updating the issue view to help you get more done. 

On a singlenode cluster, all mapreduce runs appear as "KILLED"

Description

This has been observed with the SportResults, when launching the mapreduce job with a runtime argument "league=foo" (a partition that does not exist in the input fileset).
The correct status should be "FAILED".

Worse, when the mapreduce successfully completes, the apps/<app>/mapreduce/<mapreduce>/runs endpoint shows a "KILLED" status, instead of "COMPLETED".

This does not happen in standalone.

Release Notes

None

Activity

Show:
Albert Shau
March 21, 2015, 1:27 AM

reproduceable with the PurchaseHistory example as well

Priyanka Nambiar
March 21, 2015, 2:31 AM
Sagar Kapare
March 21, 2015, 4:49 AM

COMPLETED runs were incorrectly getting marked as KILLED. Fixed this issue in the above PR. There is already another jira for failed mapreduce programs getting marked as COMPLETED : https://issues.cask.co/browse/CDAP-1745.

Marking this issue as resolved fixed.

Assignee

Sagar Kapare

Reporter

Julien Guery

Labels

None

Docs Impact

None

UX Impact

None

Fix versions

Priority

Blocker
Configure