[ https://issues.apache.org/jira/browse/OOZIE-2644?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16396450#comment-16396450 ]
Hadoop QA commented on OOZIE-2644: ---------------------------------- PreCommit-OOZIE-Build started > Skip queuing Notification Commands when there's nothing to notify > ----------------------------------------------------------------- > > Key: OOZIE-2644 > URL: https://issues.apache.org/jira/browse/OOZIE-2644 > Project: Oozie > Issue Type: Improvement > Affects Versions: 3.1.3 > Reporter: Robert Kanter > Assignee: Azrael Seoeun > Priority: Major > Fix For: trunk > > Attachments: OOZIE-2644.1.patch, OOZIE-2644.2.patch > > > When you use the > [Workflow|https://oozie.apache.org/docs/4.2.0/WorkflowFunctionalSpec.html#a5_Workflow_Notifications] > or > [Coordinator|https://oozie.apache.org/docs/4.2.0/CoordinatorFunctionalSpec.html#a15._Coordinator_Notifications] > Notification features, Oozie can end up queuing up a lot of > {{WorkflowNotificationXCommand}} and {{CoordActionNotificationXCommand}}. > This happens even if there's no notification configured on the job (which I > imagine is most of the time); in this case, the {{execute}} method simply > does nothing. This is wasteful and clogs the queue up. > We should change the code so that it doesn't queue up one of these Commands > unless there's actually a URL to notify. -- This message was sent by Atlassian JIRA (v7.6.3#76005)