[jira] Subscription: Oozie Patch Available

2014-10-07 Thread jira
Issue Subscription Filter: Oozie Patch Available (0 issues) Subscriber: ooziedaily You may edit this subscription at: https://issues.apache.org/jira/secure/FilterSubscription!default.jspa?subId=16327filterId=12325939

[jira] [Commented] (OOZIE-1981) Oozie Could not locate Oozie sharelib]

2014-10-07 Thread Amithsha (JIRA)
[ https://issues.apache.org/jira/browse/OOZIE-1981?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14161671#comment-14161671 ] Amithsha commented on OOZIE-1981: - hi all, i solved that error by adding as SHAH mentioned

[jira] [Created] (OOZIE-2027) Disable re-runs using the workflow directly if it has a parent

2014-10-07 Thread Jaydeep Vishwakarma (JIRA)
Jaydeep Vishwakarma created OOZIE-2027: -- Summary: Disable re-runs using the workflow directly if it has a parent Key: OOZIE-2027 URL: https://issues.apache.org/jira/browse/OOZIE-2027 Project:

[jira] [Created] (OOZIE-2028) Rerun with -failed option should rerun existing workflow with RERUN_FAIL_NODES=true

2014-10-07 Thread Jaydeep Vishwakarma (JIRA)
Jaydeep Vishwakarma created OOZIE-2028: -- Summary: Rerun with -failed option should rerun existing workflow with RERUN_FAIL_NODES=true Key: OOZIE-2028 URL: https://issues.apache.org/jira/browse/OOZIE-2028

[jira] [Created] (OOZIE-2029) Workflow re-run with RERUN_FAIL_NODES=true should re-run only the failed nodes of the sub-workflow

2014-10-07 Thread Jaydeep Vishwakarma (JIRA)
Jaydeep Vishwakarma created OOZIE-2029: -- Summary: Workflow re-run with RERUN_FAIL_NODES=true should re-run only the failed nodes of the sub-workflow Key: OOZIE-2029 URL:

[jira] [Updated] (OOZIE-2017) On startup, StatusTransitService can transition Coordinators that were in PREPSUSPENDED to RUNNING

2014-10-07 Thread Robert Kanter (JIRA)
[ https://issues.apache.org/jira/browse/OOZIE-2017?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Kanter updated OOZIE-2017: - Attachment: OOZIE-2017.patch The new patch has a very similar fix, but for the new

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

2014-10-07 Thread Apache Jenkins Server
See https://builds.apache.org/job/oozie-trunk-precommit-build/2026/ -- [...truncated 10123 lines...] [INFO] already added, skipping [INFO] share already added, skipping [INFO] share/lib already added, skipping [INFO] already added, skipping [INFO] share

[jira] [Commented] (OOZIE-2017) On startup, StatusTransitService can transition Coordinators that were in PREPSUSPENDED to RUNNING

2014-10-07 Thread Hadoop QA (JIRA)
[ https://issues.apache.org/jira/browse/OOZIE-2017?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14162389#comment-14162389 ] Hadoop QA commented on OOZIE-2017: -- Testing JIRA OOZIE-2017 Cleaning local git workspace

[jira] [Commented] (OOZIE-1847) HA - Oozie servers should shutdown (or go in safe mode) in case of ZK failure

2014-10-07 Thread Hadoop QA (JIRA)
[ https://issues.apache.org/jira/browse/OOZIE-1847?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14162455#comment-14162455 ] Hadoop QA commented on OOZIE-1847: -- Testing JIRA OOZIE-1847 Cleaning local git workspace

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

2014-10-07 Thread Apache Jenkins Server
See https://builds.apache.org/job/oozie-trunk-precommit-build/2027/ -- [...truncated 10117 lines...] [INFO] share already added, skipping [INFO] share/lib already added, skipping [INFO] already added, skipping [INFO] share already added, skipping [INFO]

OOZIE-2023 and 4.1 release

2014-10-07 Thread bowen zhang
Hi Purshotam, [OOZIE-2023] Job rerun can stuck in prep - ASF JIRA this is the remaining task we need to get it done for 4.1 release. Do you have latest update on this? It's in patch available state. Thanks, Bowen [OOZIE-2023] Job rerun can stuck in prep - ASF JIRA Job rerun is

[jira] [Commented] (OOZIE-2017) On startup, StatusTransitService can transition Coordinators that were in PREPSUSPENDED to RUNNING

2014-10-07 Thread Robert Kanter (JIRA)
[ https://issues.apache.org/jira/browse/OOZIE-2017?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14162515#comment-14162515 ] Robert Kanter commented on OOZIE-2017: -- Test failures unrelated On startup,

[jira] [Commented] (OOZIE-1847) HA - Oozie servers should shutdown (or go in safe mode) in case of ZK failure

2014-10-07 Thread Ryota Egashira (JIRA)
[ https://issues.apache.org/jira/browse/OOZIE-1847?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14162535#comment-14162535 ] Ryota Egashira commented on OOZIE-1847: --- test case failure unrelated. ran fine

Re: OOZIE-2023 and 4.1 release

2014-10-07 Thread Robert Kanter
Are you sure that's the remaining task? I see 7 tasks currently targeting the 4.1 release: http://s.apache.org/oozie4.1 On Tue, Oct 7, 2014 at 1:41 PM, bowen zhang bowenzhang...@yahoo.com.invalid wrote: Hi Purshotam, [OOZIE-2023] Job rerun can stuck in prep - ASF JIRA this is the remaining

[jira] [Updated] (OOZIE-2026) fix synchronization in SLACalculatorMemory.addJobStatus to avoid duplicated SLA message

2014-10-07 Thread Ryota Egashira (JIRA)
[ https://issues.apache.org/jira/browse/OOZIE-2026?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ryota Egashira updated OOZIE-2026: -- Description: race condition found where job notification fix synchronization in

[jira] [Commented] (OOZIE-1847) HA - Oozie servers should shutdown (or go in safe mode) in case of ZK failure

2014-10-07 Thread Purshotam Shah (JIRA)
[ https://issues.apache.org/jira/browse/OOZIE-1847?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14162678#comment-14162678 ] Purshotam Shah commented on OOZIE-1847: --- Thanks Ryota for committing. HA - Oozie

[jira] [Updated] (OOZIE-2026) fix synchronization in SLACalculatorMemory.addJobStatus to avoid duplicated SLA message

2014-10-07 Thread Ryota Egashira (JIRA)
[ https://issues.apache.org/jira/browse/OOZIE-2026?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ryota Egashira updated OOZIE-2026: -- Description: there is case where job generates start event by SLACalculatorMemory.addJobStatus,

[jira] [Commented] (OOZIE-2017) On startup, StatusTransitService can transition Coordinators that were in PREPSUSPENDED to RUNNING

2014-10-07 Thread Purshotam Shah (JIRA)
[ https://issues.apache.org/jira/browse/OOZIE-2017?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14162686#comment-14162686 ] Purshotam Shah commented on OOZIE-2017: --- +1 On startup, StatusTransitService can

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

2014-10-07 Thread Apache Jenkins Server
See https://builds.apache.org/job/oozie-trunk-precommit-build/2028/changes Changes: [ryota.egashira] Amendment to OOZIE-1847 -- [...truncated 9516 lines...] [INFO] share/lib already added, skipping [INFO] already added, skipping [INFO] share already

[jira] [Commented] (OOZIE-2009) Requeue CoordActionInputCheck in case of permission error

2014-10-07 Thread Hadoop QA (JIRA)
[ https://issues.apache.org/jira/browse/OOZIE-2009?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14162689#comment-14162689 ] Hadoop QA commented on OOZIE-2009: -- Testing JIRA OOZIE-2009 Cleaning local git workspace

[jira] [Commented] (OOZIE-2026) fix synchronization in SLACalculatorMemory.addJobStatus to avoid duplicated SLA message

2014-10-07 Thread Hadoop QA (JIRA)
[ https://issues.apache.org/jira/browse/OOZIE-2026?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14162825#comment-14162825 ] Hadoop QA commented on OOZIE-2026: -- Testing JIRA OOZIE-2026 Cleaning local git workspace

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

2014-10-07 Thread Apache Jenkins Server
See https://builds.apache.org/job/oozie-trunk-precommit-build/2029/ -- [...truncated 10130 lines...] [INFO] share/lib already added, skipping [INFO] already added, skipping [INFO] share already added, skipping [INFO] share/lib already added, skipping

Re: OOZIE-2023 and 4.1 release

2014-10-07 Thread bowen zhang
Excluding my blocker of publishing oozie artifacts, we agreed in a previous email a couple weeks ago that anything with no patch or active development will not be considered for 4.1 once the deadline is passed. From: Robert Kanter rkan...@cloudera.com To:

Re: OOZIE-2023 and 4.1 release

2014-10-07 Thread Robert Kanter
ah, ok. Then can you change the versions on the other JIRAs to be trunk? On Tue, Oct 7, 2014 at 5:13 PM, bowen zhang bowenzhang...@yahoo.com wrote: Excluding my blocker of publishing oozie artifacts, we agreed in a previous email a couple weeks ago that anything with no patch or active

[jira] [Updated] (OOZIE-1993) Rerun fails during join in certain condition

2014-10-07 Thread Bowen Zhang (JIRA)
[ https://issues.apache.org/jira/browse/OOZIE-1993?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bowen Zhang updated OOZIE-1993: --- Fix Version/s: (was: 4.1.0) trunk Rerun fails during join in certain

[jira] [Updated] (OOZIE-1896) ZKUUIDService - Too many job submission fails

2014-10-07 Thread Bowen Zhang (JIRA)
[ https://issues.apache.org/jira/browse/OOZIE-1896?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bowen Zhang updated OOZIE-1896: --- Fix Version/s: (was: 4.1.0) trunk ZKUUIDService - Too many job submission