[
https://issues.apache.org/jira/browse/OOZIE-2017?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14165628#comment-14165628
]
Rohini Palaniswamy commented on OOZIE-2017:
-------------------------------------------
[~rkanter],
As this is a wrong behavior, I think you should check in your initial patch
into 4.1 so that the issue is fixed there as well.
> 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, 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)
