[
https://issues.apache.org/jira/browse/OOZIE-1379?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mona Chitnis updated OOZIE-1379:
--------------------------------
Attachment: OOZIE-1379.patch
> Generate SLA end_miss event only after confirming against persistent store
> --------------------------------------------------------------------------
>
> Key: OOZIE-1379
> URL: https://issues.apache.org/jira/browse/OOZIE-1379
> Project: Oozie
> Issue Type: Sub-task
> Reporter: Mona Chitnis
> Assignee: Mona Chitnis
> Attachments: OOZIE-1379.patch, OOZIE-1379.patch
>
>
> 1. SLA status "MISS" which occurs on an END_MISS i.e. job overshot expected
> end time, is the most important sla notification for the user. We should make
> sure against the source of truth i.e. database, that the scenario is indeed
> correct for an end_miss, before setting the SLA status and sending out alerts
> for it
> 2. hanging job id getter and setter in SLASummaryBean to getId and setId to
> be consistent with getter in SLARegistrationBean
> 3. Fix bug where when Coordinator action goes from WAITING->KILLED directly,
> no event is received
--
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
