[ https://issues.apache.org/jira/browse/OOZIE-2589?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15426972#comment-15426972 ]
Robert Kanter commented on OOZIE-2589: -------------------------------------- I looked into this some more. This is actually a big problem because the callbacks can be delayed quite a while in a really really busy Oozie Server. The original priority was 2, but OOZIE-2126 accidentally changed it to 1. The 3 argument constructor is fine as-is (it doesn't take a priority so the middle priority is fine) and seems to only be used by tests anyway. > CompletedActionXCommand priority param is of no effect > ------------------------------------------------------ > > Key: OOZIE-2589 > URL: https://issues.apache.org/jira/browse/OOZIE-2589 > Project: Oozie > Issue Type: Bug > Components: core > Affects Versions: trunk > Reporter: Linflytang > Labels: patch > Fix For: 4.4.0 > > Attachments: 0001-Fixed-CompletedActionXCommand-priority-param.patch > > > CompletedActionXCommand priority param is hard coding with 1, but create the > action with 2 (HIGH_PRIORITY). > patch:https://github.com/apache/oozie/pull/20/files -- This message was sent by Atlassian JIRA (v6.3.4#6332)