Details
-
Bug
-
Status: Open
-
Minor
-
Resolution: Unresolved
-
2.0.3-alpha, 0.23.6
-
None
-
None
Description
If JobImpl enters the SUCCEEDED, FAILED, or KILLED state but then encounters an invalid state transition, it could double-count the job since jobs that encounter an error are considered failed jobs. Therefore the job could be counted initially as a successful, failed, or killed job, respectively, then counted again as a failed job due to the internal error afterwards.
Attachments
Issue Links
- relates to
-
MAPREDUCE-4825 JobImpl.finished doesn't expect ERROR as a final job state
- Closed