[
https://issues.apache.org/jira/browse/OOZIE-1913?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14096118#comment-14096118
]
Mona Chitnis commented on OOZIE-1913:
-------------------------------------
Want to mention another point:
this API also allows to disable for "ALL" sla instances for a coordinator or
bundle. For bundle, that would mean all coordinators' all actions.
SLARegistrationBean stores 'parentId' if the sla object pertains to
coord-action/wf-action/bundle-action. To avoid heavy dB query in case of the
suspend ALL for bundle(s) case, I want to change this 'parentId' to point to
bundle jobId directly, if coordinator is part of a bundle. If not, it will be
coord job id as it is now.
The impact this has is in JMSSLAEventListener, where topicName is set to this
parentId. So topicName will get set to top-level bundle-id, and user will have
to change topic name being listened to. Please give feedback if this is a
reasonable approach. I will make sure appropriate JMS selector options are
available, if user gives this bundle id topicName, but still wants to limit per
coordinator job id.
> Devise a way to turn off SLA alerts for bundle/coordinator flexibly
> -------------------------------------------------------------------
>
> Key: OOZIE-1913
> URL: https://issues.apache.org/jira/browse/OOZIE-1913
> Project: Oozie
> Issue Type: Improvement
> Affects Versions: trunk
> Reporter: Mona Chitnis
> Assignee: Mona Chitnis
> Fix For: trunk
>
>
> From user:
> Need to turn off the SLA miss alerts in jobs when the bundle is suspended for
> grid upgrades and similar work so that when it's resumed we aren't flooded
> with a bunch of alerts.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
