You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@oozie.apache.org by "Robert Kanter (JIRA)" <ji...@apache.org> on 2014/07/02 00:35:24 UTC

[jira] [Created] (OOZIE-1912) HCatAccessor waits for JMS notifications even if there aren't going to be any

Robert Kanter created OOZIE-1912:
------------------------------------

             Summary: HCatAccessor waits for JMS notifications even if there aren't going to be any
                 Key: OOZIE-1912
                 URL: https://issues.apache.org/jira/browse/OOZIE-1912
             Project: Oozie
          Issue Type: Bug
    Affects Versions: trunk
            Reporter: Robert Kanter


We saw that even if you don't have HCat publishing notifications to JMS, Oozie can still listen for them.  This is a problem because it can then take up to 10min for Oozie to realize that an HCat data dependency has been met (i.e. using the fallback polling).  It should instead be using the regular polling, which is a 1min interval.

It looks like the problem is that oozie-default sets {{oozie.service.HCatAccessorService.jmsconnections}} a connection defined for {{default=...}}, which then gets mapped to any HCat URI, so Oozie always thinks that every HCat URI will publish JMS messages.  By setting it to blank (i.e. " " space), we were able to fix this.  I think the default value of this property should be space, not {{default=...}}.



--
This message was sent by Atlassian JIRA
(v6.2#6252)