Hi, Oozie normally checks that an action has finished by receiving a callback from the JobTracker (or ResourceManager). However, if it for some reason doesn't receive the callback, it has a fallback procedure where it checks at 10min intervals. It sounds like you might not be getting the callbacks, so it's taking 10 minutes for an action to end. Can you check your Oozie log to see if it's receiving callbacks? Search for messages mentioning the "CallbackService". You can also look in the JobTracker (or ResourceManager) logs to see if there's something happening on that end; search for messages mentioning "callback" or "notification" (I'm not sure exactly what they call it there).
- Robert On Fri, Jun 27, 2014 at 10:19 AM, Jonathan Hodges <[email protected]> wrote: > Hi, > > We have noticed some pauses between execution of action steps in our Oozie > workflows. A job may take a couple minutes yet the next step isn't > triggered for sometimes ten minutes. Is there a way to control this pause? > We have a set of jobs that when executed at a command-line runs for about > 45 mins. The same set of jobs in Oozie is over 3 hours. > > We tried setting the following properties, but we aren't using coordinators > so it didn't help. > > oozie.service.CoordMaterializeTriggerService.lookup.interval=30 > oozie.service.CoordMaterializeTriggerService.materialization.window=7200 > > Is there maybe similar properties at the workflow level we can set? > > Thanks so much, > > Jonathan >
