[OOZIE-1244] SLA Support in Oozie

• Type: New Feature
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Fix Version/s: 4.0.0
• Component/s: monitoring
• Assignee: Ryota Egashira
• Reporter: Rohini Palaniswamy
• Created: 01/Mar/13 19:34
• Updated: 18/Dec/15 08:19
• Resolved: 20/May/13 16:52

Description

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.

Issue Links

• depends upon: OOZIE-1296 SLA JMS Event Listener for publishing notifications related to SLA information
• depends upon: OOZIE-1294 SLA Email Notification
• relates to: OOZIE-1768 Workflow schema 0.4.5 was removed
• requires: OOZIE-1375 Generate Job notification events for Workflow Actions
• requires: OOZIE-1364 Fix duplicate events generated and fields missing in events
• links to: ReviewBoard

Sub-Tasks

• SLA Documentation: Closed
• SLA Bootstrap Service: Resolved
• Extend SLA tag support to Coordinator Job and Bundle Job: Resolved
• Generate SLA end_miss event only after confirming against persistent store: Resolved
• Improve memory footprint of Calculator Memory object: Open
• REST API to fetch SLA: Closed
• Fix flakey SLA tests: Closed
• UI for SLA: Closed
• Coordinator job change command not removing SLA Registration bean: Closed
• Fix bugs around ActionKillX not setting end time, V2SLAServlet and exception handling for event threads: Closed
• fix bug in SLARegistrationBean and CoordActionsCountForJobIdJPAExecutor: Closed
• Implement SLA Bootstrap Service and fix bugs in SLACalculator: Closed
• Handle reruns for SLA notifications: Closed
• Improve SLA reliability on restart, fix bugs related to SLA and event generation: Closed
• Fix bugs in SLA UI: Closed
• Fix bugs in SLA UI: Closed
• Fix bugs related to coordchange and parentId in events: Closed
• Remove SLACalculatorBean and add columns to SummaryBean indicating events processed and sla processed: Closed
• Make <should-end> optional in SLA for users only concerned about <duration>: Open
• Purge rogue and stale entries from history set: Open
• SLACalcStatus not updating the last modified time correctly and duplicate DURATION_* event: Resolved
• Duplicate Coord_Action events on Waiting -> Timeout, and Coord Materialize not removing actions on Failure: Closed
• Confirm against database before generating start and duration miss events: Resolved
• Duplicate end_miss events introduced by OOZIE-1472: Closed