Hi Ram,

Like I said in the thread Matteo linked to, when it takes ~10min, that's a
pretty good indicator that the callbacks are not getting through.  Please
see my explanation of that in the other thread.

You can change the checking interval, but that puts extra stress on
Yarn/JT.
See oozie.service.ActionCheckerService.action.check.interval and
oozie.service.ActionCheckerService.action.check.delay
https://github.com/apache/oozie/blob/master/core/src/main/resources/oozie-default.xml#L1610

- Robert

On Mon, Sep 14, 2015 at 3:17 AM, Matteo Luzzi <[email protected]>
wrote:

> I am not sure whether is possible to set an update interval, as far as I
> know oozie should get updates from hadoop when there is a change in the job
> status via callbacks. Maybe someone with more experience than me can
> provide a better answer.
>
> Matteo
>
> 2015-09-14 11:53 GMT+02:00 ram kumar <[email protected]>:
>
> > thanks Matteo,
> >
> > Each job gets updated every 10 minutes in oozie console.
> > It doesn't automatically update, when job completes.
> > Is it possible to how to change config to like 5 minutes ?
> >
> > On Mon, Sep 14, 2015 at 12:12 PM, Matteo Luzzi <[email protected]>
> > wrote:
> >
> > > Hi,
> > > maybe you are facing my same problem, that hadoop notification
> callbacks
> > > are not correctly sent to oozie server. Finally I discovered that I was
> > > messing a bit with oozie url properties and I solved my problem. You
> can
> > > check here
> > >
> > >
> >
> http://mail-archives.apache.org/mod_mbox/oozie-user/201508.mbox/%3CCALBGZ8qveCuxrmYyX%2BkxO1bYCZA5zf_0p8hJk5t_BUsj44S78w%40mail.gmail.com%3E
> > >
> > > regards,
> > > Matteo
> > >
> > > 2015-09-14 7:47 GMT+02:00 ram kumar <[email protected]>:
> > >
> > > > Hi,
> > > >
> > > > when trying oozie workflow sequentially,
> > > > after first job completion, it shows in hadoop console job succeeded.
> > > > But, it takes around 5 minutes to update in oozie console.
> > > >
> > > >
> > > > can you help me with it?
> > > >
> > > > Thanks
> > > >
> > >
> > >
> > >
> > > --
> > > Matteo Remo Luzzi
> > >
> >
>
>
>
> --
> Matteo Remo Luzzi
>

Reply via email to