[
https://issues.apache.org/jira/browse/OOZIE-1244?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13633863#comment-13633863
]
Mona Chitnis commented on OOZIE-1244:
-------------------------------------
Starting to take a stab at code. Reviewboard -
https://reviews.apache.org/r/10569/
1. Revisiting the SLA handling in Oozie
2. Addition of a calculator service to process sla events in a continuous
fashion
3. Added new oozie-sla schema v0.2, to replace confusing <sla-id> with the
correct one <job-id> and removing unused tags <parent-client-id> etc..
WIP:
1. Making sure SLA events - registration as well as job status - are generated
from all places
2. Building on top of Ryota's patch OOZIE-1296, SLAEvent class might be removed
from this patch and put in 1296
3. Unit tests
4. Renaming "event_id" to "sequenceId" in JSONSLAEvent giving below compilation
error - tracing its root
{code}
13/04/17 00:05:52 ERROR openjpa.Runtime: No field or getter method for
attribute "event_id" can be found in "class
org.apache.oozie.client.rest.JsonSLAEvent".
<openjpa-2.1.0-r422266:1071316 nonfatal user error>
org.apache.openjpa.util.UserException: No field or getter method for attribute
"event_id" can be found in "class org.apache.oozie.client.rest.JsonSLAEvent".
at
org.apache.openjpa.persistence.PersistenceMetaDataDefaults.error(PersistenceMetaDataDefaults.java:559)
at
org.apache.openjpa.persistence.PersistenceMetaDataDefaults.getMemberByProperty(PersistenceMetaDataDefaults.java:684)
at
org.apache.openjpa.persistence.XMLPersistenceMetaDataParser.parseField(XMLPersistenceMetaDataParser.java:1253)
at
org.apache.openjpa.persistence.XMLPersistenceMetaDataParser.startId(XMLPersistenceMetaDataParser.java:1068)
at
org.apache.openjpa.persistence.XMLPersistenceMetaDataParser.startClassElement(XMLPersistenceMetaDataParser.java:663)
at
org.apache.openjpa.lib.meta.CFMetaDataParser.startElement(CFMetaDataParser.java:111)
at
org.apache.openjpa.lib.meta.XMLMetaDataParser.startElement(XMLMetaDataParser.java:449)
at
com.sun.org.apache.xerces.internal.parsers.AbstractSAXParser.startElement(AbstractSAXParser.java:501)
at
com.sun.org.apache.xerces.internal.impl.xs.XMLSchemaValidator.startElement(XMLSchemaValidator.java:714)
at
com.sun.org.apache.xerces.internal.impl.XMLNSDocumentScannerImpl.scanStartElement(XMLNSDocumentScannerImpl.java:400)
...
at
org.apache.tools.ant.dispatch.DispatchUtils.execute(DispatchUtils.java:106)
{code}
> 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: 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
