[
https://issues.apache.org/jira/browse/OOZIE-1244?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mona Chitnis updated OOZIE-1244:
--------------------------------
Attachment: OOZIE-1244.patch
Final patch with addressing all comments from Mohammad, Virag and Rohini.
Highlights:
1. Made the 'historySet' storing expunged job-ids as a synchronizedSet for
thread-safety
2. Removed jms/sla/event classes from oozie-site
3. Not passing EntityManager to EventHandler since we cannot share EM out of
the transaction context executed per XCommand (every execute creates new EM
context and performs em.commit()). The atomicity of writes of jobs and their
events can be done only by including Event beans in the same insert/updatelist
during XCommands themselves --> later JIRA
4. Resolved Jenkins issues of Tabs/>132 long lines/javac warnings
Testing: unit tests + end-to-end tests done and pass
> SLA Support in Oozie
> --------------------
>
> Key: OOZIE-1244
> URL: https://issues.apache.org/jira/browse/OOZIE-1244
> Project: Oozie
> Issue Type: New Feature
> Reporter: Rohini Palaniswamy
> Assignee: Ryota Egashira
> Attachments: OOZIE-1244.patch, OOZIE-1244.patch,
> OozieMonitoring-929-1244.pptx
>
>
> Would like to have the following features in Oozie
> - JMS notifications on SLA met, SLA start miss, SLA end miss and SLA
> duration miss
> - Email alerting for SLA start miss, SLA end miss and SLA duration miss
> - API to query SLA met/miss information. Currently the SLA information that
> can be queried is only SLA registration event and job status events. One has
> to calculate the actual misses from those.
> - A simple dashboard to view and query the SLA met/miss information built on
> the API mentioned above.
--
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
