[
https://issues.apache.org/jira/browse/OOZIE-2017?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14144113#comment-14144113
]
Hadoop QA commented on OOZIE-2017:
----------------------------------
Testing JIRA OOZIE-2017
Cleaning local git workspace
----------------------------
{color:green}+1 PATCH_APPLIES{color}
{color:green}+1 CLEAN{color}
{color:green}+1 RAW_PATCH_ANALYSIS{color}
. {color:green}+1{color} the patch does not introduce any @author tags
. {color:green}+1{color} the patch does not introduce any tabs
. {color:green}+1{color} the patch does not introduce any trailing spaces
. {color:green}+1{color} the patch does not introduce any line longer than
132
. {color:green}+1{color} the patch does adds/modifies 1 testcase(s)
{color:green}+1 RAT{color}
. {color:green}+1{color} the patch does not seem to introduce new RAT
warnings
{color:green}+1 JAVADOC{color}
. {color:green}+1{color} the patch does not seem to introduce new Javadoc
warnings
{color:green}+1 COMPILE{color}
. {color:green}+1{color} HEAD compiles
. {color:green}+1{color} patch compiles
. {color:green}+1{color} the patch does not seem to introduce new javac
warnings
{color:green}+1 BACKWARDS_COMPATIBILITY{color}
. {color:green}+1{color} the patch does not change any JPA
Entity/Colum/Basic/Lob/Transient annotations
. {color:green}+1{color} the patch does not modify JPA files
{color:red}-1 TESTS{color}
. Tests run: 1530
. Tests failed: 2
. Tests errors: 0
. The patch failed the following testcases:
.
testCoordStatusTransitServiceSuspendedWithError(org.apache.oozie.service.TestStatusTransitService)
.
testNone(org.apache.oozie.command.coord.TestCoordActionInputCheckXCommandNonUTC)
{color:green}+1 DISTRO{color}
. {color:green}+1{color} distro tarball builds with the patch
----------------------------
{color:red}*-1 Overall result, please check the reported -1(s)*{color}
The full output of the test-patch run is available at
. https://builds.apache.org/job/oozie-trunk-precommit-build/2002/
> 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)
