You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@oozie.apache.org by "michelle chiang (JIRA)" <ji...@apache.org> on 2012/11/14 01:20:12 UTC
[jira] [Created] (OOZIE-1065) bundle status does not transit after
rerun
michelle chiang created OOZIE-1065:
--------------------------------------
Summary: bundle status does not transit after rerun
Key: OOZIE-1065
URL: https://issues.apache.org/jira/browse/OOZIE-1065
Project: Oozie
Issue Type: Bug
Components: bundle
Affects Versions: 3.3.0
Reporter: michelle chiang
Priority: Minor
2 similar cases.
1. submit a bundle, with 3 coord jobs. kill coord-job-1.
coord-job-1 becomes KILLED with both actions KILLED.
the other 2 coord jobs finished SUCCEEDED. and bundle job is DONEWITHERROR.
rerun bundle job, -coordinator=coord-job-1. as soon as the rerun command is issued, bundle job status is RUNNINGWITHERROR.
because coord-job-1 is in KILLED, it cannot be rerun.
but bundle job stays in RUNNINGWITHERROR when all 3 coord jobs in terminal states (KILLED, SUCCEEDED, SUCCEEDED).
kill the bundle job. then bundle transit to KILLED for a second, then back to RUNNINGWITHERROR.
2. submit a bundle, with 3 coord jobs. kill coord-job-1.
coord-job-1 becomes DONEWITHERROR with 1 action SUCCEEDED, and 1 action KILLED.
the other 2 coord jobs finished SUCCEEDED. and bundle job is DONEWITHERROR.
rerun bundle job, -coordinator=coord-job-1. as soon as the rerun command is issued, bundle job status is RUNNINGWITHERROR.
coord-job-1 is in RUNNING after rerun.
but bundle job stays in RUNNINGWITHERROR, and does not transit to RUNNING, when 1 coord job RUNNING and other 2 coord job SUCCEEDED.
and bundle job stays in RUNNINGWITHERROR when all 3 coord jobs in terminal states (DONEWITHERROR, SUCCEEDED, SUCCEEDED).
kill the bundle job. then bundle transit to KILLED for a second, then back to RUNNINGWITHERROR.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (OOZIE-1065) bundle status does not transit
after rerun
Posted by "Hadoop QA (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/OOZIE-1065?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13506949#comment-13506949 ]
Hadoop QA commented on OOZIE-1065:
----------------------------------
Testing JIRA OOZIE-1065
Cleaning local svn 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:green}+1 TESTS{color}
. Tests run: 923
{color:green}+1 DISTRO{color}
. {color:green}+1{color} distro tarball builds with the patch
----------------------------
{color:green}*+1 Overall result, good!, no -1s*{color}
The full output of the test-patch run is available at
. https://builds.apache.org/job/oozie-trunk-precommit-build/218/
> bundle status does not transit after rerun
> ------------------------------------------
>
> Key: OOZIE-1065
> URL: https://issues.apache.org/jira/browse/OOZIE-1065
> Project: Oozie
> Issue Type: Bug
> Components: bundle
> Affects Versions: 3.3.0
> Reporter: michelle chiang
> Assignee: Virag Kothari
> Priority: Minor
> Attachments: OOZIE-1065.patch
>
>
> 2 similar cases.
> 1. submit a bundle, with 3 coord jobs. kill coord-job-1.
> coord-job-1 becomes KILLED with both actions KILLED.
> the other 2 coord jobs finished SUCCEEDED. and bundle job is DONEWITHERROR.
> rerun bundle job, -coordinator=coord-job-1. as soon as the rerun command is issued, bundle job status is RUNNINGWITHERROR.
> because coord-job-1 is in KILLED, it cannot be rerun.
> but bundle job stays in RUNNINGWITHERROR when all 3 coord jobs in terminal states (KILLED, SUCCEEDED, SUCCEEDED).
> kill the bundle job. then bundle transit to KILLED for a second, then back to RUNNINGWITHERROR.
> 2. submit a bundle, with 3 coord jobs. kill coord-job-1.
> coord-job-1 becomes DONEWITHERROR with 1 action SUCCEEDED, and 1 action KILLED.
> the other 2 coord jobs finished SUCCEEDED. and bundle job is DONEWITHERROR.
> rerun bundle job, -coordinator=coord-job-1. as soon as the rerun command is issued, bundle job status is RUNNINGWITHERROR.
> coord-job-1 is in RUNNING after rerun.
> but bundle job stays in RUNNINGWITHERROR, and does not transit to RUNNING, when 1 coord job RUNNING and other 2 coord job SUCCEEDED.
> and bundle job stays in RUNNINGWITHERROR when all 3 coord jobs in terminal states (DONEWITHERROR, SUCCEEDED, SUCCEEDED).
> kill the bundle job. then bundle transit to KILLED for a second, then back to RUNNINGWITHERROR.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (OOZIE-1065) bundle status does not transit after
rerun
Posted by "Virag Kothari (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/OOZIE-1065?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Virag Kothari updated OOZIE-1065:
---------------------------------
Attachment: OOZIE-1065.patch
When rerun cmd is issued on killed coordinator, the bundle action pending flag is not reset. Hence the state transition of bundle is not happening. The patch calls the the parent of the killed coordinator to reset its pending flag.
Patch for review at
https://reviews.apache.org/r/8282/
> bundle status does not transit after rerun
> ------------------------------------------
>
> Key: OOZIE-1065
> URL: https://issues.apache.org/jira/browse/OOZIE-1065
> Project: Oozie
> Issue Type: Bug
> Components: bundle
> Affects Versions: 3.3.0
> Reporter: michelle chiang
> Priority: Minor
> Attachments: OOZIE-1065.patch
>
>
> 2 similar cases.
> 1. submit a bundle, with 3 coord jobs. kill coord-job-1.
> coord-job-1 becomes KILLED with both actions KILLED.
> the other 2 coord jobs finished SUCCEEDED. and bundle job is DONEWITHERROR.
> rerun bundle job, -coordinator=coord-job-1. as soon as the rerun command is issued, bundle job status is RUNNINGWITHERROR.
> because coord-job-1 is in KILLED, it cannot be rerun.
> but bundle job stays in RUNNINGWITHERROR when all 3 coord jobs in terminal states (KILLED, SUCCEEDED, SUCCEEDED).
> kill the bundle job. then bundle transit to KILLED for a second, then back to RUNNINGWITHERROR.
> 2. submit a bundle, with 3 coord jobs. kill coord-job-1.
> coord-job-1 becomes DONEWITHERROR with 1 action SUCCEEDED, and 1 action KILLED.
> the other 2 coord jobs finished SUCCEEDED. and bundle job is DONEWITHERROR.
> rerun bundle job, -coordinator=coord-job-1. as soon as the rerun command is issued, bundle job status is RUNNINGWITHERROR.
> coord-job-1 is in RUNNING after rerun.
> but bundle job stays in RUNNINGWITHERROR, and does not transit to RUNNING, when 1 coord job RUNNING and other 2 coord job SUCCEEDED.
> and bundle job stays in RUNNINGWITHERROR when all 3 coord jobs in terminal states (DONEWITHERROR, SUCCEEDED, SUCCEEDED).
> kill the bundle job. then bundle transit to KILLED for a second, then back to RUNNINGWITHERROR.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Assigned] (OOZIE-1065) bundle status does not transit after
rerun
Posted by "Virag Kothari (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/OOZIE-1065?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Virag Kothari reassigned OOZIE-1065:
------------------------------------
Assignee: Virag Kothari
> bundle status does not transit after rerun
> ------------------------------------------
>
> Key: OOZIE-1065
> URL: https://issues.apache.org/jira/browse/OOZIE-1065
> Project: Oozie
> Issue Type: Bug
> Components: bundle
> Affects Versions: 3.3.0
> Reporter: michelle chiang
> Assignee: Virag Kothari
> Priority: Minor
> Attachments: OOZIE-1065.patch
>
>
> 2 similar cases.
> 1. submit a bundle, with 3 coord jobs. kill coord-job-1.
> coord-job-1 becomes KILLED with both actions KILLED.
> the other 2 coord jobs finished SUCCEEDED. and bundle job is DONEWITHERROR.
> rerun bundle job, -coordinator=coord-job-1. as soon as the rerun command is issued, bundle job status is RUNNINGWITHERROR.
> because coord-job-1 is in KILLED, it cannot be rerun.
> but bundle job stays in RUNNINGWITHERROR when all 3 coord jobs in terminal states (KILLED, SUCCEEDED, SUCCEEDED).
> kill the bundle job. then bundle transit to KILLED for a second, then back to RUNNINGWITHERROR.
> 2. submit a bundle, with 3 coord jobs. kill coord-job-1.
> coord-job-1 becomes DONEWITHERROR with 1 action SUCCEEDED, and 1 action KILLED.
> the other 2 coord jobs finished SUCCEEDED. and bundle job is DONEWITHERROR.
> rerun bundle job, -coordinator=coord-job-1. as soon as the rerun command is issued, bundle job status is RUNNINGWITHERROR.
> coord-job-1 is in RUNNING after rerun.
> but bundle job stays in RUNNINGWITHERROR, and does not transit to RUNNING, when 1 coord job RUNNING and other 2 coord job SUCCEEDED.
> and bundle job stays in RUNNINGWITHERROR when all 3 coord jobs in terminal states (DONEWITHERROR, SUCCEEDED, SUCCEEDED).
> kill the bundle job. then bundle transit to KILLED for a second, then back to RUNNINGWITHERROR.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (OOZIE-1065) bundle status does not transit after
rerun
Posted by "Alejandro Abdelnur (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/OOZIE-1065?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Alejandro Abdelnur updated OOZIE-1065:
--------------------------------------
Fix Version/s: (was: 3.3.0)
3.3.1
> bundle status does not transit after rerun
> ------------------------------------------
>
> Key: OOZIE-1065
> URL: https://issues.apache.org/jira/browse/OOZIE-1065
> Project: Oozie
> Issue Type: Bug
> Components: bundle
> Affects Versions: 3.3.0
> Reporter: michelle chiang
> Assignee: Virag Kothari
> Priority: Minor
> Fix For: 3.3.1
>
> Attachments: OOZIE-1065.patch
>
>
> 2 similar cases.
> 1. submit a bundle, with 3 coord jobs. kill coord-job-1.
> coord-job-1 becomes KILLED with both actions KILLED.
> the other 2 coord jobs finished SUCCEEDED. and bundle job is DONEWITHERROR.
> rerun bundle job, -coordinator=coord-job-1. as soon as the rerun command is issued, bundle job status is RUNNINGWITHERROR.
> because coord-job-1 is in KILLED, it cannot be rerun.
> but bundle job stays in RUNNINGWITHERROR when all 3 coord jobs in terminal states (KILLED, SUCCEEDED, SUCCEEDED).
> kill the bundle job. then bundle transit to KILLED for a second, then back to RUNNINGWITHERROR.
> 2. submit a bundle, with 3 coord jobs. kill coord-job-1.
> coord-job-1 becomes DONEWITHERROR with 1 action SUCCEEDED, and 1 action KILLED.
> the other 2 coord jobs finished SUCCEEDED. and bundle job is DONEWITHERROR.
> rerun bundle job, -coordinator=coord-job-1. as soon as the rerun command is issued, bundle job status is RUNNINGWITHERROR.
> coord-job-1 is in RUNNING after rerun.
> but bundle job stays in RUNNINGWITHERROR, and does not transit to RUNNING, when 1 coord job RUNNING and other 2 coord job SUCCEEDED.
> and bundle job stays in RUNNINGWITHERROR when all 3 coord jobs in terminal states (DONEWITHERROR, SUCCEEDED, SUCCEEDED).
> kill the bundle job. then bundle transit to KILLED for a second, then back to RUNNINGWITHERROR.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira