[jira] [Commented] (OOZIE-1476) Add ability to issue kill on Coordinator Action directly
[ https://issues.apache.org/jira/browse/OOZIE-1476?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13724873#comment-13724873 ] Virag Kothari commented on OOZIE-1476: -- Instead of reusing the API for coord job kill, I think we should have different API. Also we should allow specifying range of actions to kill (similar to rerun API). oozie job -kill -action 5-20 This will make it extensible and more parameters later on like -date and -appName can be added. > Add ability to issue kill on Coordinator Action directly > > > Key: OOZIE-1476 > URL: https://issues.apache.org/jira/browse/OOZIE-1476 > Project: Oozie > Issue Type: Improvement >Affects Versions: trunk >Reporter: Mona Chitnis >Assignee: Mona Chitnis >Priority: Minor > Fix For: trunk > > Attachments: OOZIE-1476_branch4.patch, OOZIE-1476.patch > > Original Estimate: 48h > Remaining Estimate: 48h > > If we want to kill a coordinator action in particular, there is no way to do > this currently. Kill has to be issued on the Coordinator Job level and > percolates through to all its actions. This JIRA is enhancing the kill > command for coord action specifically. -- 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
Oozie 3.3.2 + hadoop 2.0.4-alpha failure
Hi all , My team is new to Oozie. We have successfully build Oozie 3.3.2 with hadoop 2.0.4-alpha by modifying multiple pom.xml to add hadoop 2.0.4-alpha. We also used command "mvn clean package -Dhadoop.version=2.0.4-alpha" for build. However multiple unit testcases, as listed below, are failing. Are these known issues? Does Oozie 3.3.2 support hadoop 2.x? any help would be greatly appreciated.. Running org.apache.oozie.action.hadoop.TestHiveActionExecutor Tests run: 3, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 19.861 sec <<< FAILURE! Running org.apache.oozie.command.wf.TestActionCheckXCommand Tests run: 8, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 15.282 sec <<< FAILURE! Running org.apache.oozie.action.hadoop.TestLauncher Tests run: 10, Failures: 7, Errors: 0, Skipped: 0, Time elapsed: 60.42 sec <<< FAILURE! Running org.apache.oozie.action.hadoop.TestMapReduceActionError Tests run: 3, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 9.757 sec <<< FAILURE! Running org.apache.oozie.action.hadoop.TestDistCpActionExecutor Tests run: 1, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 8.055 sec <<< FAILURE! Running org.apache.oozie.service.TestRecoveryService Tests run: 7, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 46.539 sec <<< FAILURE! Running org.apache.oozie.action.hadoop.TestJavaActionExecutor Tests run: 25, Failures: 9, Errors: 0, Skipped: 0, Time elapsed: 156.315 sec <<< FAILURE! Running org.apache.oozie.command.wf.TestActionStartXCommand Tests run: 6, Failures: 2, Errors: 0, Skipped: 0, Time elapsed: 24.878 sec <<< FAILURE! Running org.apache.oozie.action.hadoop.TestShellActionExecutor Tests run: 6, Failures: 3, Errors: 1, Skipped: 0, Time elapsed: 34.981 sec <<< FAILURE! Running org.apache.oozie.action.hadoop.TestMapReduceActionExecutor Tests run: 12, Failures: 6, Errors: 0, Skipped: 0, Time elapsed: 59.235 sec <<< FAILURE! Running org.apache.oozie.action.hadoop.TestRerun Tests run: 1, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 121.987 sec <<< FAILURE! Running org.apache.oozie.action.hadoop.TestHiveMain Tests run: 1, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 37.348 sec <<< FAILURE! Results : Failed tests: testHiveAction (org.apache.oozie.action.hadoop.TestHiveActionExecutor) testActionCheck(org.apache.oozie.command.wf.TestActionCheckXCommand) testOutput(org.apache.oozie.action.hadoop.TestLauncher) testExit0(org.apache.oozie.action.hadoop.TestLauncher) testExit1(org.apache.oozie.action.hadoop.TestLauncher) testEmpty(org.apache.oozie.action.hadoop.TestLauncher) testException(org.apache.oozie.action.hadoop.TestLauncher) testNewId(org.apache.oozie.action.hadoop.TestLauncher) testSecurityManager(org.apache.oozie.action.hadoop.TestLauncher) testDistCpFile(org.apache.oozie.action.hadoop.TestDistCpActionExecutor) testWorkflowActionRecoveryUserRetry (org.apache.oozie.service.TestRecoveryService) testOutputSubmitOK(org.apache.oozie.action.hadoop.TestJavaActionExecutor) testRecovery(org.apache.oozie.action.hadoop.TestJavaActionExecutor): expected:<...ob_1375223658833_002[0]> but was:<...ob_1375223658833_002[1]> testAdditionalJarSubmitOK (org.apache.oozie.action.hadoop.TestJavaActionExecutor) testSimpestSleSubmitOK (org.apache.oozie.action.hadoop.TestJavaActionExecutor) testIdSwapSubmitOK(org.apache.oozie.action.hadoop.TestJavaActionExecutor) testExit0SubmitOK(org.apache.oozie.action.hadoop.TestJavaActionExecutor) testExit1SubmitError (org.apache.oozie.action.hadoop.TestJavaActionExecutor) testExceptionSubmitError (org.apache.oozie.action.hadoop.TestJavaActionExecutor) testPrepare(org.apache.oozie.action.hadoop.TestJavaActionExecutor) testActionWithEscapedStringAndCDATA (org.apache.oozie.command.wf.TestActionStartXCommand) testActionStart(org.apache.oozie.command.wf.TestActionStartXCommand) testShellScript(org.apache.oozie.action.hadoop.TestShellActionExecutor) testShellScriptError (org.apache.oozie.action.hadoop.TestShellActionExecutor) testPerlScript(org.apache.oozie.action.hadoop.TestShellActionExecutor) testSetExecutionStats_when_user_has_specified_stats_write_TRUE (org.apache.oozie.action.hadoop.TestMapReduceActionExecutor) testSetExecutionStats_when_user_has_specified_stats_write_FALSE (org.apache.oozie.action.hadoop.TestMapReduceActionExecutor) testMapReduce(org.apache.oozie.action.hadoop.TestMapReduceActionExecutor) testMapReduceWithCredentials (org.apache.oozie.action.hadoop.TestMapReduceActionExecutor) testStreaming(org.apache.oozie.action.hadoop.TestMapReduceActionExecutor) testSetMapredJobName (org.apache.oozie.action.hadoop.TestMapReduceActionExecutor) testRerun(org.apache.oozie.action.hadoop.TestRerun): expected: but was: testMain(org.apache.oozie.action.hadoop.TestHiveMain) Tests in error: testMapReduce(org.apache.oozie.action.hadoop.TestMapReduceActionError) testEnvVar(org.apache.oozie.action.hadoop.TestShellActionExecutor): str cannot be null Tests run: 929, Failures: 33, Error
[jira] [Updated] (OOZIE-1476) Add ability to issue kill on Coordinator Action directly
[ https://issues.apache.org/jira/browse/OOZIE-1476?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mona Chitnis updated OOZIE-1476: Attachment: OOZIE-1476_branch4.patch > Add ability to issue kill on Coordinator Action directly > > > Key: OOZIE-1476 > URL: https://issues.apache.org/jira/browse/OOZIE-1476 > Project: Oozie > Issue Type: Improvement >Affects Versions: trunk >Reporter: Mona Chitnis >Assignee: Mona Chitnis >Priority: Minor > Fix For: trunk > > Attachments: OOZIE-1476_branch4.patch, OOZIE-1476.patch > > Original Estimate: 48h > Remaining Estimate: 48h > > If we want to kill a coordinator action in particular, there is no way to do > this currently. Kill has to be issued on the Coordinator Job level and > percolates through to all its actions. This JIRA is enhancing the kill > command for coord action specifically. -- 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-1476) Add ability to issue kill on Coordinator Action directly
[ https://issues.apache.org/jira/browse/OOZIE-1476?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mona Chitnis updated OOZIE-1476: Attachment: OOZIE-1476.patch > Add ability to issue kill on Coordinator Action directly > > > Key: OOZIE-1476 > URL: https://issues.apache.org/jira/browse/OOZIE-1476 > Project: Oozie > Issue Type: Improvement >Affects Versions: trunk >Reporter: Mona Chitnis >Assignee: Mona Chitnis >Priority: Minor > Fix For: trunk > > Attachments: OOZIE-1476_branch4.patch, OOZIE-1476.patch > > Original Estimate: 48h > Remaining Estimate: 48h > > If we want to kill a coordinator action in particular, there is no way to do > this currently. Kill has to be issued on the Coordinator Job level and > percolates through to all its actions. This JIRA is enhancing the kill > command for coord action specifically. -- 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
Review Request 13097: OOZIE-1476 Add ability to issue kill on Coordinator Action directly
--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/13097/ --- Review request for oozie. Bugs: OOZIE-1476 https://issues.apache.org/jira/browse/OOZIE-1476 Repository: oozie Description --- See JIRA OOZIE-1476 Diffs - trunk/core/src/main/java/org/apache/oozie/CoordinatorEngine.java 1508679 trunk/core/src/main/java/org/apache/oozie/command/KillTransitionXCommand.java 1508679 trunk/core/src/main/java/org/apache/oozie/command/RerunTransitionXCommand.java 1508679 trunk/core/src/main/java/org/apache/oozie/command/bundle/BundleJobChangeXCommand.java 1508679 trunk/core/src/main/java/org/apache/oozie/command/coord/CoordActionCheckXCommand.java 1508679 trunk/core/src/main/java/org/apache/oozie/command/coord/CoordActionKillXCommand.java PRE-CREATION trunk/core/src/main/java/org/apache/oozie/command/coord/CoordChangeXCommand.java 1508679 trunk/core/src/main/java/org/apache/oozie/command/coord/CoordRerunXCommand.java 1508679 trunk/core/src/main/java/org/apache/oozie/executor/jpa/WorkflowJobGetForSLAJPAExecutor.java 1508679 trunk/core/src/main/java/org/apache/oozie/executor/jpa/WorkflowJobGetForSmallObjJPAExecutor.java PRE-CREATION trunk/core/src/main/java/org/apache/oozie/service/StatusTransitService.java 1508679 trunk/core/src/main/java/org/apache/oozie/servlet/V1JobServlet.java 1508679 trunk/core/src/main/java/org/apache/oozie/sla/SLACalculatorMemory.java 1508679 trunk/core/src/main/java/org/apache/oozie/util/StatusUtils.java 1508679 trunk/core/src/test/java/org/apache/oozie/command/coord/TestCoordActionKillXCommand.java PRE-CREATION Diff: https://reviews.apache.org/r/13097/diff/ Testing --- added unit tests Thanks, Mona Chitnis
[jira] [Updated] (OOZIE-1479) Duplicate end_miss events introduced by OOZIE-1472
[ https://issues.apache.org/jira/browse/OOZIE-1479?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rohini Palaniswamy updated OOZIE-1479: -- Attachment: OOZIE-1479-2.patch > Duplicate end_miss events introduced by OOZIE-1472 > -- > > Key: OOZIE-1479 > URL: https://issues.apache.org/jira/browse/OOZIE-1479 > Project: Oozie > Issue Type: Sub-task >Reporter: Rohini Palaniswamy >Assignee: Rohini Palaniswamy > Fix For: 4.0.0 > > Attachments: OOZIE-1479-1.patch, OOZIE-1479-2.patch > > -- 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
Re: Review Request 13030: [OOZIE-1471] Support glob in FS action and prepare blocks
--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/13030/ --- (Updated July 30, 2013, 9:15 p.m.) Review request for oozie. Changes --- -fixed issue in prepare-block -add support of glob in chgrp and chmod -introduce max limit in # of globbed files/dirs (default to 1000), to avoid flawed workflow causing huge pressure on NN. if exceeds limit, workflow fails with error message indicating hitting limit Bugs: OOZIE-1471 https://issues.apache.org/jira/browse/OOZIE-1471 Repository: oozie Description --- https://issues.apache.org/jira/browse/OOZIE-1471 Diffs (updated) - trunk/core/src/main/java/org/apache/oozie/action/hadoop/FsActionExecutor.java 1507396 trunk/core/src/main/java/org/apache/oozie/action/hadoop/JavaActionExecutor.java 1507396 trunk/core/src/main/java/org/apache/oozie/action/hadoop/LauncherMapperHelper.java 1507396 trunk/core/src/test/java/org/apache/oozie/action/hadoop/TestFSPrepareActions.java 1507396 trunk/core/src/test/java/org/apache/oozie/action/hadoop/TestFsActionExecutor.java 1507396 trunk/sharelib/oozie/src/main/java/org/apache/oozie/action/hadoop/FSLauncherURIHandler.java 1507396 trunk/sharelib/oozie/src/main/java/org/apache/oozie/action/hadoop/LauncherMapper.java 1507396 trunk/sharelib/oozie/src/main/java/org/apache/oozie/action/hadoop/PrepareActionsDriver.java 1507396 Diff: https://reviews.apache.org/r/13030/diff/ Testing (updated) --- run sample workflow on local cluster. Thanks, Ryota Egashira
[jira] [Updated] (OOZIE-1479) Duplicate end_miss events introduced by OOZIE-1472
[ https://issues.apache.org/jira/browse/OOZIE-1479?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rohini Palaniswamy updated OOZIE-1479: -- Attachment: OOZIE-1479-1.patch > Duplicate end_miss events introduced by OOZIE-1472 > -- > > Key: OOZIE-1479 > URL: https://issues.apache.org/jira/browse/OOZIE-1479 > Project: Oozie > Issue Type: Sub-task >Reporter: Rohini Palaniswamy >Assignee: Rohini Palaniswamy > Fix For: 4.0.0 > > Attachments: OOZIE-1479-1.patch > > -- 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] [Created] (OOZIE-1479) Duplicate end_miss events introduced by OOZIE-1472
Rohini Palaniswamy created OOZIE-1479: - Summary: Duplicate end_miss events introduced by OOZIE-1472 Key: OOZIE-1479 URL: https://issues.apache.org/jira/browse/OOZIE-1479 Project: Oozie Issue Type: Sub-task Reporter: Rohini Palaniswamy Assignee: Rohini Palaniswamy -- 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-1478) Some commands display incorrect LogInfo in acquireLock statements
[ https://issues.apache.org/jira/browse/OOZIE-1478?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mona Chitnis updated OOZIE-1478: Issue Type: Sub-task (was: Bug) Parent: OOZIE-1474 > Some commands display incorrect LogInfo in acquireLock statements > - > > Key: OOZIE-1478 > URL: https://issues.apache.org/jira/browse/OOZIE-1478 > Project: Oozie > Issue Type: Sub-task >Affects Versions: trunk, 4.0.0 >Reporter: Mona Chitnis >Assignee: Mona Chitnis > Fix For: trunk, 4.0.0 > > > In XCommand execute(), the order is this > eagerLoadState() > eagerVerifyPreCondition() > acquireLock() > loadState() > verifyPreCondition() > All of these generate Log statements with JOB and ACTION ids populated. > However in most commands, loadState() is where LogInfo is updated with the > correct JOB and ACTION ids, hence preceding statements can show old LogInfo > of some other job. > The resetPrefix() is not working as expected. -- 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
