[ https://issues.apache.org/jira/browse/OOZIE-2017?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14158547#comment-14158547 ]
Purshotam Shah commented on OOZIE-2017: --------------------------------------- {quote} I took a quick look at OOZIE-1940, it makes a lot of changes, including completely removing the code I was fixing I double-checked and the incorrect transition can still happen though. I'll have to look through the new code more thoroughly to fix it again. {quote} Yes, i didn't fix that because I knew that you have patch ready for that :-) > On startup, StatusTransitService can transition Coordinators that were in > PREPSUSPENDED to RUNNING > -------------------------------------------------------------------------------------------------- > > Key: OOZIE-2017 > URL: https://issues.apache.org/jira/browse/OOZIE-2017 > Project: Oozie > Issue Type: Bug > Components: coordinator > Affects Versions: trunk, 4.0.0 > Reporter: Robert Kanter > Assignee: Robert Kanter > Priority: Critical > Fix For: trunk > > Attachments: OOZIE-2017.patch, OOZIE-2017.patch > > > 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. -- This message was sent by Atlassian JIRA (v6.3.4#6332)