[
https://issues.apache.org/jira/browse/OOZIE-2650?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15432090#comment-15432090
]
Hadoop QA commented on OOZIE-2650:
----------------------------------
Testing JIRA OOZIE-2650
Cleaning local git 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 2 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: 1794
. Tests failed: 1
. Tests errors: 0
. The patch failed the following testcases:
.
testCoordStatus_Killed(org.apache.oozie.command.coord.TestCoordChangeXCommand)
{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/3235/
> Retry coord start on database exceptions
> ----------------------------------------
>
> Key: OOZIE-2650
> URL: https://issues.apache.org/jira/browse/OOZIE-2650
> Project: Oozie
> Issue Type: Bug
> Reporter: Satish Subhashrao Saley
> Assignee: Satish Subhashrao Saley
> Attachments: OOZIE-2650-1.patch
>
>
> {code:title=CoordActionStartXCommand.java}
> updateList.add(new UpdateEntry<WorkflowJobQuery>(
> WorkflowJobQuery.UPDATE_WORKFLOW_PARENT_MODIFIED,
> wfJob));
> updateList.add(new UpdateEntry<CoordActionQuery>(
> CoordActionQuery.UPDATE_COORD_ACTION_FOR_START,
> coordAction));
> try {
> executor.executeBatchInsertUpdateDelete(insertList,
> updateList, null);
> queue(new
> CoordActionNotificationXCommand(coordAction), 100);
> if (EventHandlerService.isEnabled()) {
> generateEvent(coordAction, user, appName,
> wfJob.getStartTime());
> }
> }
> catch (JPAExecutorException je) {
> throw new CommandException(je);
> }
> .........
> .......
> ........
> finally {
> if (makeFail == true) { // No DB exception occurs
> ....
> ....
> ....
> queue(new
> CoordActionReadyXCommand(coordAction.getJobId()));
> }
> }
> {code}
> If there is any Database issue while starting coord action, we fail the coord
> action. We should retry.
> CoordActionStartXCommand submits workflow. Workflow gets linked to the coord
> action if workflow submission succeeds. But if coord action update fails due
> to database exception, recovery service should be able to recover it.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
