[OOZIE-2017] On startup, StatusTransitService can transition Coordinators that were in PRESUSPENDED to RUNNING

• Type: Bug
• Status: Closed
• Priority: Critical
• Resolution: Fixed
• Affects Version/s: trunk, 4.0.0
• Fix Version/s: 4.1.0
• Component/s: coordinator
• Assignee: Robert Kanter
• Reporter: Robert Kanter
• Created: 22/Sep/14 19:38
• Updated: 03/Nov/16 12:00
• Resolved: 08/Oct/14 20:25

Description

You can reproduce this issue easily:

1. Submit a coordinator job that starts in the future
   • It enters PREP state
2. Suspend the coordinator job
   • It enters PREPSUSPENDED state
3. 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:

1. PREPSUSPENDED --> RUNNING is not a valid transition (it has to go to PREP first)
2. It shouldn't resume by itself

The log shows that the StatusTransitService is doing it.