Re: issue after OOZIE-1807

Right now what is in the trunk and 4.1 branch, the bundle will go into "DONEWIHTERROR" stage From: Mona Chitnis To: Rohini Palaniswamy ; "dev@oozie.apache.org" Cc: bowen zhang Sent: Thursday, September 18, 2014 5:49 PM Subject: Re: issue after OOZIE-1807

Re: issue after OOZIE-1807

>if a bundle with two actions - one FAILED due to coordinator submission >error, other KILLED), bundle is supposed to KILLED bq. Bundle should be >FAILED and not KILLED. Only when user has KILLED the bundle, should >its >status be KILLED. Currently if one of coord job submit fails, Oozie will is

Re: issue after OOZIE-1807

bq. if a bundle with two actions - one FAILED due to coordinator submission error, other KILLED), bundle is supposed to KILLED bq.   Bundle should be FAILED and not KILLED. Only when user has KILLED the bundle, should its status be KILLED. Thanks for minor correction. I was shooting for bundle

Re: issue after OOZIE-1807

bq. Shouldn't oozie be intelligent enough to do a no-op on a killed coord job? There are options now to resume a killed coord job. If new end time was applied on other coord jobs and not applied on that one, user needs to know. bq. if a bundle with two actions - one FAILED due to coordinator su

[jira] [Commented] (OOZIE-1813) Add service to report/kill rogue bundles and coordinator jobs

[ https://issues.apache.org/jira/browse/OOZIE-1813?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14139775#comment-14139775 ] Rohini Palaniswamy commented on OOZIE-1813: --- +1. The longer lines are named quer

Build failed in Jenkins: oozie-trunk-precommit-build #1994

See -- [...truncated 9480 lines...] [INFO] share/lib already added, skipping [INFO] already added, skipping [INFO] share already added, skipping [INFO] share/lib already added, skipping [INFO

[jira] [Commented] (OOZIE-1813) Add service to report/kill rogue bundles and coordinator jobs

[ https://issues.apache.org/jira/browse/OOZIE-1813?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14139688#comment-14139688 ] Hadoop QA commented on OOZIE-1813: -- Testing JIRA OOZIE-1813 Cleaning local git workspace

Re: issue after OOZIE-1807

Bowen, JIRA has explanation. Please update JIRA if you see any issue with approach. >Why is it a good idea to throw an exception if one of the coord jobs is >in "killed" state? In the BundleJobChangeXCommand, the code doesn't even >attempt to change the coord job. Shouldn't oozie be intelligent >e

[jira] [Updated] (OOZIE-2013) Bundle job with children status of "KILLED" and "FAILED" should transition to "KILLED" instead of "DONEWITHERROR"

[ https://issues.apache.org/jira/browse/OOZIE-2013?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bowen Zhang updated OOZIE-2013: --- Attachment: oozie-2013.patch > Bundle job with children status of "KILLED" and "FAILED" should transit

Build failed in Jenkins: oozie-trunk-precommit-build #1993

See Changes: [rkanter] OOZIE-1917 Authentication secret should be random by default and needs to coordinate with HA (rkanter) -- [...truncated 9596 lines...] [INFO] share/lib already

[jira] [Commented] (OOZIE-1813) Add service to report/kill rogue bundles and coordinator jobs

[ https://issues.apache.org/jira/browse/OOZIE-1813?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14139638#comment-14139638 ] Hadoop QA commented on OOZIE-1813: -- Testing JIRA OOZIE-1813 Cleaning local git workspace

[jira] [Commented] (OOZIE-2013) Bundle job with children status of "KILLED" and "FAILED" should transition to "KILLED" instead of "DONEWITHERROR"

[ https://issues.apache.org/jira/browse/OOZIE-2013?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14139637#comment-14139637 ] Purshotam Shah commented on OOZIE-2013: --- Job status as "killed" indicate that job is

[jira] [Updated] (OOZIE-2013) Bundle job with children status of "KILLED" and "FAILED" should transition to "KILLED" instead of "DONEWITHERROR"

[ https://issues.apache.org/jira/browse/OOZIE-2013?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bowen Zhang updated OOZIE-2013: --- Summary: Bundle job with children status of "KILLED" and "FAILED" should transition to "KILLED" instea

[jira] [Created] (OOZIE-2013) Bundle job with children status of "KILLED" and "FAILED" should transition to "KILLED" instead of "DONEIWTHERROR"

Bowen Zhang created OOZIE-2013: -- Summary: Bundle job with children status of "KILLED" and "FAILED" should transition to "KILLED" instead of "DONEIWTHERROR" Key: OOZIE-2013 URL: https://issues.apache.org/jira/browse/O

Re: Review Request 25788: OOZIE-2009 Requeue CoordActionInputCheck in case of permission error

--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/25788/#review53881 --- Ship it! >LOG.info("Permission error in ActionInputCheck: " + e.get

Re: Review Request 25788: OOZIE-2009 Requeue CoordActionInputCheck in case of permission error

--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/25788/ --- (Updated Sept. 18, 2014, 9:58 p.m.) Review request for oozie and Purshotam Shah

Re: issue after OOZIE-1807

Hi Purshotam, Why is it a good idea to throw an exception if one of the coord jobs is in "killed" state? In the BundleJobChangeXCommand, the code doesn't even attempt to change the coord job. Shouldn't oozie be intelligent enough to do a no-op on a killed coord job? Bowen

[jira] [Commented] (OOZIE-1813) Add service to report/kill rogue bundles and coordinator jobs

[ https://issues.apache.org/jira/browse/OOZIE-1813?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14139486#comment-14139486 ] Purshotam Shah commented on OOZIE-1813: --- {quote} Tests failed: 1 . Tests errors: 0 .

[jira] [Updated] (OOZIE-1813) Add service to report/kill rogue bundles and coordinator jobs

[ https://issues.apache.org/jira/browse/OOZIE-1813?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Purshotam Shah updated OOZIE-1813: -- Attachment: OOZIE-1813-Amendment-V1.patch > Add service to report/kill rogue bundles and coordin

Re: Review Request 25788: OOZIE-2009 Requeue CoordActionInputCheck in case of permission error

--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/25788/ --- (Updated Sept. 18, 2014, 7:16 p.m.) Review request for oozie and Purshotam Shah

Review Request 25788: OOZIE-2009 Requeue CoordActionInputCheck in case of permission error

--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/25788/ --- Review request for oozie and Purshotam Shah. Bugs: OOZIE-2009 https://issue

[jira] [Commented] (OOZIE-1795) Please create a DOAP file for your TLP

[ https://issues.apache.org/jira/browse/OOZIE-1795?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14139240#comment-14139240 ] Sebb commented on OOZIE-1795: - OK, should be fixed now. It will take about a day to show up.

[jira] [Commented] (OOZIE-1977) Display patch analysis issues

[ https://issues.apache.org/jira/browse/OOZIE-1977?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14139239#comment-14139239 ] Robert Kanter commented on OOZIE-1977: -- I see. Can you update the patch to either pu

[jira] [Commented] (OOZIE-1795) Please create a DOAP file for your TLP

[ https://issues.apache.org/jira/browse/OOZIE-1795?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14139204#comment-14139204 ] Sebb commented on OOZIE-1795: - Thanks for reporting this - it looks like the projects build pr

[jira] [Commented] (OOZIE-1940) StatusTransitService has race condition

[ https://issues.apache.org/jira/browse/OOZIE-1940?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14138664#comment-14138664 ] Hadoop QA commented on OOZIE-1940: -- Testing JIRA OOZIE-1940 Cleaning local git workspace

Build failed in Jenkins: oozie-trunk-precommit-build #1992

See -- [...truncated 10135 lines...] [INFO] share/lib already added, skipping [INFO] already added, skipping [INFO] share already added, skipping [INFO] share/lib already added, skipping [INF

Jenkins build is back to normal : oozie-trunk-find-patches-available #74681

See

Build failed in Jenkins: oozie-trunk-find-patches-available #74680

See -- Started by timer Building remotely on H1 (Mapreduce Hadoop Pig Hdfs) in workspace > git rev-parse --is-i