[
https://issues.apache.org/jira/browse/OOZIE-2026?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14162825#comment-14162825
]
Hadoop QA commented on OOZIE-2026:
----------------------------------
Testing JIRA OOZIE-2026
Cleaning local git 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:green}+1{color} the patch does not introduce any line longer than
132
. {color:red}-1{color} the patch does not add/modify any testcase
{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: 1535
. Tests failed: 2
. Tests errors: 0
. The patch failed the following testcases:
.
testActionKillCommandDate(org.apache.oozie.command.coord.TestCoordActionsKillXCommand)
.
testMemoryUsageAndSpeed(org.apache.oozie.service.TestPartitionDependencyManagerService)
{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/2029/
> fix synchronization in SLACalculatorMemory.addJobStatus to avoid duplicated
> SLA message
> ---------------------------------------------------------------------------------------
>
> Key: OOZIE-2026
> URL: https://issues.apache.org/jira/browse/OOZIE-2026
> Project: Oozie
> Issue Type: Bug
> Reporter: Ryota Egashira
> Assignee: Ryota Egashira
> Attachments: OOZIE-2016.patch
>
>
> there is case where job generates start event by
> SLACalculatorMemory.addJobStatus, but before eventProcessed flag updated on
> DB side, SLA worker thread picks the action
> (SLACalculatorMemory.updateJobSla), end up sending duplicated messages. this
> patch is to fix synchronized block in addJobStatus to prevent this.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
