[jira] [Commented] (OOZIE-2668) Status update and recovery problems when coord action and its children not in sync

["Hadoop QA (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/OOZIE-2668?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15537741#comment-15537741 ] 

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 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: 1814
.    Tests failed: 7
.    Tests errors: 0

.    The patch failed the following testcases:

.      testBulkCoordSuspendResumeKillSuccess(org.apache.oozie.command.coord.TestBulkCoordXCommand)
.      testCoordKillSuccess2(org.apache.oozie.command.coord.TestCoordKillXCommand)
.      testCoordKillSuccess3(org.apache.oozie.command.coord.TestCoordKillXCommand)
.      testCoordKillForBackwardSupport(org.apache.oozie.command.coord.TestCoordKillXCommand)
.      testCoordActionInputCheckXCommandUniqueness(org.apache.oozie.command.coord.TestCoordActionInputCheckXCommandNonUTC)
.      testNone(org.apache.oozie.command.coord.TestCoordActionInputCheckXCommand)
.      testBundleStatusTransitServiceKilled2(org.apache.oozie.service.TestStatusTransitService)

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

> 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, OOZIE-2668-4.patch, OOZIE-2688-3.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
(v6.3.4#6332)