Hadoop QA commented on OOZIE-2668:

Testing JIRA OOZIE-2668

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 
.    {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 
{color:green}+1 JAVADOC{color}
.    {color:green}+1{color} the patch does not seem to introduce new Javadoc 
{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 
{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: 1805
.    Tests failed: 5
.    Tests errors: 3

.    The patch failed the following testcases:

.      testMain(org.apache.oozie.action.hadoop.TestHiveMain)
.      testPigScript(org.apache.oozie.action.hadoop.TestPigMain)
.      testPig_withNullExternalID(org.apache.oozie.action.hadoop.TestPigMain)
.      testEmbeddedPigWithinPython(org.apache.oozie.action.hadoop.TestPigMain)
.      testPigScript(org.apache.oozie.action.hadoop.TestPigMainWithOldAPI)

{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/3286/

> Status update and recovery problems when coord action and its children not in 
> sync
> ----------------------------------------------------------------------------------
>                 Key: OOZIE-2668
>                 URL: https://issues.apache.org/jira/browse/OOZIE-2668
>             Project: Oozie
>          Issue Type: Bug
>            Reporter: Satish Subhashrao Saley
>            Assignee: Satish Subhashrao Saley
>         Attachments: OOZIE-2668-1.patch, OOZIE-2668-2.patch
> In cases where workflow is already in terminal status (except failed) but the 
> coord action is not yet updated and still running, following will happen if a 
> kill command is issued on the coord job: 
> Kill on Coordjob will make the kill on coordaction pending until the children 
> are also killed. However, as the wf in terminal state (except failed), the wf 
> will not be killed and preverifycondition will fail. The wf doesn't update 
> its parent and hence the coordaction kill will still be pending. Two 
> problems: Status transit service will not resolve the state of this coord job 
> as some the actions are still pending Recovery service will try to recover 
> this killed coord action and keep on reissuing the kill command.

This message was sent by Atlassian JIRA

Reply via email to