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 00:48:13 UTC
[jira] [Created] (OOZIE-1064) coord job status should not transit
after kill
michelle chiang created OOZIE-1064:
--------------------------------------
Summary: coord job status should not transit after kill
Key: OOZIE-1064
URL: https://issues.apache.org/jira/browse/OOZIE-1064
Project: Oozie
Issue Type: Bug
Components: coordinator
Affects Versions: 3.3.0
Reporter: michelle chiang
Priority: Minor
coord job status should not transit after coord_kill.
to reproduce:
submit a bundle job which has 3 catchup-mode coord jobs, and each coord job has 3 actions.
kill 1 coord job as soon as its first action SUCCEEDED while coord job is RUNNING.
the coord job status becomes KILLED for a second, with only 1 SUCCEEDED action.
then it transit to SUCCEEDED.
--
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-1064) Status value of coordinator job not
reflected in bundle action and invalid transition of coordinator job
Posted by "Virag Kothari (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/OOZIE-1064?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Virag Kothari updated OOZIE-1064:
---------------------------------
Attachment: OOZIE-1064.patch
> Status value of coordinator job not reflected in bundle action and invalid transition of coordinator job
> ---------------------------------------------------------------------------------------------------------
>
> Key: OOZIE-1064
> URL: https://issues.apache.org/jira/browse/OOZIE-1064
> Project: Oozie
> Issue Type: Bug
> Components: coordinator
> Affects Versions: 3.3.0
> Reporter: michelle chiang
> Assignee: Virag Kothari
> Priority: Minor
> Attachments: OOZIE-1064.patch
>
>
> The status of coordinator job is not reflected correctly in bundle action when coordinator job is in terminal state. Also the coordinator job should transit to SUCCEEDED only when materialization is done
> to reproduce:
> submit a bundle job which has 3 catchup-mode coord jobs, and each coord job has 3 actions.
> kill 1 coord job as soon as its first action SUCCEEDED while coord job is RUNNING.
> the coord job status becomes KILLED for a second, with only 1 SUCCEEDED action.
> then it transit to SUCCEEDED.
> the bundle job's other 2 coord jobs finished SUCCEEDED.
> however the final bundle job status is DONEWITHERROR (which is correct since the 1 coord job should be KILLED),
> when all 3 coord jobs displayed status as SUCCEEDED.
--
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-1064) coord job status should not transit
after kill
Posted by "michelle chiang (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/OOZIE-1064?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
michelle chiang updated OOZIE-1064:
-----------------------------------
Description:
coord job status should not transit after coord_kill.
to reproduce:
submit a bundle job which has 3 catchup-mode coord jobs, and each coord job has 3 actions.
kill 1 coord job as soon as its first action SUCCEEDED while coord job is RUNNING.
the coord job status becomes KILLED for a second, with only 1 SUCCEEDED action.
then it transit to SUCCEEDED.
the bundle job's other 2 coord jobs finished SUCCEEDED.
however the final bundle job status is DONEWITHERROR (which is correct since the 1 coord job should be KILLED),
when all 3 coord jobs displayed status as SUCCEEDED.
was:
coord job status should not transit after coord_kill.
to reproduce:
submit a bundle job which has 3 catchup-mode coord jobs, and each coord job has 3 actions.
kill 1 coord job as soon as its first action SUCCEEDED while coord job is RUNNING.
the coord job status becomes KILLED for a second, with only 1 SUCCEEDED action.
then it transit to SUCCEEDED.
> coord job status should not transit after kill
> ----------------------------------------------
>
> Key: OOZIE-1064
> URL: https://issues.apache.org/jira/browse/OOZIE-1064
> Project: Oozie
> Issue Type: Bug
> Components: coordinator
> Affects Versions: 3.3.0
> Reporter: michelle chiang
> Priority: Minor
>
> coord job status should not transit after coord_kill.
> to reproduce:
> submit a bundle job which has 3 catchup-mode coord jobs, and each coord job has 3 actions.
> kill 1 coord job as soon as its first action SUCCEEDED while coord job is RUNNING.
> the coord job status becomes KILLED for a second, with only 1 SUCCEEDED action.
> then it transit to SUCCEEDED.
> the bundle job's other 2 coord jobs finished SUCCEEDED.
> however the final bundle job status is DONEWITHERROR (which is correct since the 1 coord job should be KILLED),
> when all 3 coord jobs displayed status as SUCCEEDED.
--
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-1064) Status value of coordinator job
not reflected in bundle action and invalid transition of coordinator job
Posted by "Hadoop QA (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/OOZIE-1064?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13506258#comment-13506258 ]
Hadoop QA commented on OOZIE-1064:
----------------------------------
Testing JIRA OOZIE-1064
Cleaning local svn workspace
----------------------------
{color:green}+1 PATCH_APPLIES{color}
{color:green}+1 CLEAN{color}
{color:red}-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:red}-1{color} the patch contains 1 line(s) longer than 132 characters
. {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: 924
{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/211/
> Status value of coordinator job not reflected in bundle action and invalid transition of coordinator job
> ---------------------------------------------------------------------------------------------------------
>
> Key: OOZIE-1064
> URL: https://issues.apache.org/jira/browse/OOZIE-1064
> Project: Oozie
> Issue Type: Bug
> Components: coordinator
> Affects Versions: 3.3.0
> Reporter: michelle chiang
> Assignee: Virag Kothari
> Priority: Minor
> Attachments: OOZIE-1064.patch
>
>
> The status of coordinator job is not reflected correctly in bundle action when coordinator job is in terminal state. Also the coordinator job should transit to SUCCEEDED only when materialization is done
> to reproduce:
> submit a bundle job which has 3 catchup-mode coord jobs, and each coord job has 3 actions.
> kill 1 coord job as soon as its first action SUCCEEDED while coord job is RUNNING.
> the coord job status becomes KILLED for a second, with only 1 SUCCEEDED action.
> then it transit to SUCCEEDED.
> the bundle job's other 2 coord jobs finished SUCCEEDED.
> however the final bundle job status is DONEWITHERROR (which is correct since the 1 coord job should be KILLED),
> when all 3 coord jobs displayed status as SUCCEEDED.
--
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-1064) Status value of coordinator job not
reflected in bundle action and invalid transition of coordinator job
Posted by "Virag Kothari (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/OOZIE-1064?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Virag Kothari updated OOZIE-1064:
---------------------------------
Description:
The status of coordinator job is not reflected correctly in bundle action when coordinator job is in terminal state. Also the coordinator job should transit to SUCCEEDED only when materialization is done
to reproduce:
submit a bundle job which has 3 catchup-mode coord jobs, and each coord job has 3 actions.
kill 1 coord job as soon as its first action SUCCEEDED while coord job is RUNNING.
the coord job status becomes KILLED for a second, with only 1 SUCCEEDED action.
then it transit to SUCCEEDED.
the bundle job's other 2 coord jobs finished SUCCEEDED.
however the final bundle job status is DONEWITHERROR (which is correct since the 1 coord job should be KILLED),
when all 3 coord jobs displayed status as SUCCEEDED.
was:
coord job status should not transit after coord_kill.
to reproduce:
submit a bundle job which has 3 catchup-mode coord jobs, and each coord job has 3 actions.
kill 1 coord job as soon as its first action SUCCEEDED while coord job is RUNNING.
the coord job status becomes KILLED for a second, with only 1 SUCCEEDED action.
then it transit to SUCCEEDED.
the bundle job's other 2 coord jobs finished SUCCEEDED.
however the final bundle job status is DONEWITHERROR (which is correct since the 1 coord job should be KILLED),
when all 3 coord jobs displayed status as SUCCEEDED.
Assignee: Virag Kothari
Summary: Status value of coordinator job not reflected in bundle action and invalid transition of coordinator job (was: coord job status should not transit after kill)
> Status value of coordinator job not reflected in bundle action and invalid transition of coordinator job
> ---------------------------------------------------------------------------------------------------------
>
> Key: OOZIE-1064
> URL: https://issues.apache.org/jira/browse/OOZIE-1064
> Project: Oozie
> Issue Type: Bug
> Components: coordinator
> Affects Versions: 3.3.0
> Reporter: michelle chiang
> Assignee: Virag Kothari
> Priority: Minor
> Attachments: OOZIE-1064.patch
>
>
> The status of coordinator job is not reflected correctly in bundle action when coordinator job is in terminal state. Also the coordinator job should transit to SUCCEEDED only when materialization is done
> to reproduce:
> submit a bundle job which has 3 catchup-mode coord jobs, and each coord job has 3 actions.
> kill 1 coord job as soon as its first action SUCCEEDED while coord job is RUNNING.
> the coord job status becomes KILLED for a second, with only 1 SUCCEEDED action.
> then it transit to SUCCEEDED.
> the bundle job's other 2 coord jobs finished SUCCEEDED.
> however the final bundle job status is DONEWITHERROR (which is correct since the 1 coord job should be KILLED),
> when all 3 coord jobs displayed status as SUCCEEDED.
--
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-1064) Status value of coordinator job
not reflected in bundle action and invalid transition of coordinator job
Posted by "Hadoop QA (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/OOZIE-1064?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13507052#comment-13507052 ]
Hadoop QA commented on OOZIE-1064:
----------------------------------
Testing JIRA OOZIE-1064
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:red}-1 TESTS{color}
. Tests run: 924
. Tests failed: 2
. Tests errors: 0
. The patch failed the following testcases:
. testBundleStatusTransitServiceKilled1(org.apache.oozie.service.TestStatusTransitService)
. testUnpauseBundleAndCoordinator(org.apache.oozie.service.TestPauseTransitService)
{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/221/
> Status value of coordinator job not reflected in bundle action and invalid transition of coordinator job
> ---------------------------------------------------------------------------------------------------------
>
> Key: OOZIE-1064
> URL: https://issues.apache.org/jira/browse/OOZIE-1064
> Project: Oozie
> Issue Type: Bug
> Components: coordinator
> Affects Versions: 3.3.0
> Reporter: michelle chiang
> Assignee: Virag Kothari
> Priority: Minor
> Attachments: OOZIE-1064.patch, OOZIE-1064.patch
>
>
> The status of coordinator job is not reflected correctly in bundle action when coordinator job is in terminal state. Also the coordinator job should transit to SUCCEEDED only when materialization is done
> to reproduce:
> submit a bundle job which has 3 catchup-mode coord jobs, and each coord job has 3 actions.
> kill 1 coord job as soon as its first action SUCCEEDED while coord job is RUNNING.
> the coord job status becomes KILLED for a second, with only 1 SUCCEEDED action.
> then it transit to SUCCEEDED.
> the bundle job's other 2 coord jobs finished SUCCEEDED.
> however the final bundle job status is DONEWITHERROR (which is correct since the 1 coord job should be KILLED),
> when all 3 coord jobs displayed status as SUCCEEDED.
--
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-1064) Status value of coordinator job not
reflected in bundle action and invalid transition of coordinator job
Posted by "Virag Kothari (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/OOZIE-1064?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Virag Kothari updated OOZIE-1064:
---------------------------------
Attachment: OOZIE-1064.patch
offending line > 132 chars fixed
> Status value of coordinator job not reflected in bundle action and invalid transition of coordinator job
> ---------------------------------------------------------------------------------------------------------
>
> Key: OOZIE-1064
> URL: https://issues.apache.org/jira/browse/OOZIE-1064
> Project: Oozie
> Issue Type: Bug
> Components: coordinator
> Affects Versions: 3.3.0
> Reporter: michelle chiang
> Assignee: Virag Kothari
> Priority: Minor
> Attachments: OOZIE-1064.patch, OOZIE-1064.patch
>
>
> The status of coordinator job is not reflected correctly in bundle action when coordinator job is in terminal state. Also the coordinator job should transit to SUCCEEDED only when materialization is done
> to reproduce:
> submit a bundle job which has 3 catchup-mode coord jobs, and each coord job has 3 actions.
> kill 1 coord job as soon as its first action SUCCEEDED while coord job is RUNNING.
> the coord job status becomes KILLED for a second, with only 1 SUCCEEDED action.
> then it transit to SUCCEEDED.
> the bundle job's other 2 coord jobs finished SUCCEEDED.
> however the final bundle job status is DONEWITHERROR (which is correct since the 1 coord job should be KILLED),
> when all 3 coord jobs displayed status as SUCCEEDED.
--
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-1064) Status value of coordinator job not
reflected in bundle action and invalid transition of coordinator job
Posted by "Alejandro Abdelnur (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/OOZIE-1064?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Alejandro Abdelnur updated OOZIE-1064:
--------------------------------------
Fix Version/s: (was: 3.3.0)
3.3.1
> Status value of coordinator job not reflected in bundle action and invalid transition of coordinator job
> ---------------------------------------------------------------------------------------------------------
>
> Key: OOZIE-1064
> URL: https://issues.apache.org/jira/browse/OOZIE-1064
> Project: Oozie
> Issue Type: Bug
> Components: coordinator
> Affects Versions: 3.3.0
> Reporter: michelle chiang
> Assignee: Virag Kothari
> Priority: Minor
> Fix For: 3.3.1
>
> Attachments: OOZIE-1064.patch, OOZIE-1064.patch
>
>
> The status of coordinator job is not reflected correctly in bundle action when coordinator job is in terminal state. Also the coordinator job should transit to SUCCEEDED only when materialization is done
> to reproduce:
> submit a bundle job which has 3 catchup-mode coord jobs, and each coord job has 3 actions.
> kill 1 coord job as soon as its first action SUCCEEDED while coord job is RUNNING.
> the coord job status becomes KILLED for a second, with only 1 SUCCEEDED action.
> then it transit to SUCCEEDED.
> the bundle job's other 2 coord jobs finished SUCCEEDED.
> however the final bundle job status is DONEWITHERROR (which is correct since the 1 coord job should be KILLED),
> when all 3 coord jobs displayed status as SUCCEEDED.
--
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