Details
-
Bug
-
Status: Closed
-
Critical
-
Resolution: Fixed
-
trunk, 4.0.0
-
None
Description
You can reproduce this issue easily:
- Submit a coordinator job that starts in the future
- It enters PREP state
- Suspend the coordinator job
- It enters PREPSUSPENDED state
- Restart Oozie and wait about a minute or so
- The job transitions back to RUNNING state by itself
This is the wrong behavior for two reasons:
- PREPSUSPENDED --> RUNNING is not a valid transition (it has to go to PREP first)
- It shouldn't resume by itself
The log shows that the StatusTransitService is doing it.