[
https://issues.apache.org/jira/browse/OOZIE-2850?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15949411#comment-15949411
]
Robert Kanter commented on OOZIE-2850:
--------------------------------------
That "nothing to notify" message is about the Oozie server sending out a
notification to an external program, if configured; it's not related to the
callbacks the Oozie server is waiting to receive. See
http://oozie.apache.org/docs/4.3.0/WorkflowFunctionalSpec.html#a5_Workflow_Notifications
OOZIE-2648 was only removing the callback url from the child jobs, not the
launcher job (except for MR Action where we kept it). This is important
because there are situations where you end up with a lot of child jobs (say,
hundreds) and then you'll swamp the Oozie server with unnecessary callback
checking.
It sounds like we should fix {{oozie.base.url}} to use the correct port.
> Fix default callback notifications
> ----------------------------------
>
> Key: OOZIE-2850
> URL: https://issues.apache.org/jira/browse/OOZIE-2850
> Project: Oozie
> Issue Type: Bug
> Reporter: Attila Sasvari
> Priority: Trivial
>
> Currently oozie.service.CallbackService.base.url in oozie-default.xml is set
> to use
> [oozie.base.url/callback|
> https://github.com/apache/oozie/blob/7c404ad0ea4c61e90e8c86015de25ef196168c29/core/src/main/resources/oozie-default.xml#L1639]
> which defaults to
> [http://localhost:8080/oozie|https://github.com/apache/oozie/blob/7c404ad0ea4c61e90e8c86015de25ef196168c29/core/src/main/resources/oozie-default.xml#L105].
> As a result, actions finished are not detected by default. (Jetty listens on
> HTTP port 11000, see [port in oozie-default.xml |
> https://github.com/apache/oozie/blob/7c404ad0ea4c61e90e8c86015de25ef196168c29/core/src/main/resources/oozie-default.xml#L2535])
> {{oozie.http.hostname}} and {{oozie.http.port}} could be used in
> {{oozie.base.url}}
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
