Hi, By default Oozie checks the status of every action in every 10 minutes. This would cause delays between action executions so Oozie uses the MapReduce's notification url to send a notification.
The MapReduce ApplicationMaster send the callback to the Oozie server. This callback triggers the check of the action in question, so after the callback is received by the Oozie server it makes a call to the ResourceManager. As every action is using a MapReduce launcher to execute it's logic, this mechanism is used for every action. The documentation is misleading at the first quote, I'll file a jira to clarify that. Hope it helps, gp On Thu, Apr 20, 2017 at 4:59 PM, Jean Carlo <jean.jeancar...@gmail.com> wrote: > Hi everybody, > > I am quite strugguling trying to understand oozie ha and how it use the > variable oozie_base_url. > > The documentation says > > It is used by the resourcemanager link > <https://github.com/apache/oozie/blob/7c404ad0ea4c61e90e8c86015de25e > f196168c29/docs/src/site/twiki/AG_Install.twiki#L893> > but it is very confusing because it also says it is used by the > ApplicationMaster link > <https://github.com/apache/oozie/blob/7c404ad0ea4c61e90e8c86015de25e > f196168c29/docs/src/site/twiki/AG_Install.twiki#L781> > > > What are the services that make callbacks to oozie? > > ApplicationMaster or ResourceManager ? > > > Thank you for your help > > Jean Carlo > > "The best way to predict the future is to invent it" Alan Kay > -- Peter Cseh Software Engineer <http://www.cloudera.com>
