[
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, 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. (was: race condition found where job
notification )
> 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)
