Have not come across this case before. I would suggest taking a jstack of the Oozie launcher jvm if you have access to the node to see where it is stuck.
On Wed, Aug 9, 2017 at 9:31 PM, Ronald Green <green.ron...@gmail.com> wrote: > The MR jobs usually succeed and the oozie pig launcher just stays up and > running with the last message in the log predating MR job completion : > > INFO org.apache.pig.backend.hadoop.executionengine.mapReduceLayer. > MapReduceLauncher > - Running jobs are [job_xxx] > > > On Wed, Aug 9, 2017 at 9:25 PM, Rohini Palaniswamy < > rohini.adi...@gmail.com> > wrote: > > > Are the MR jobs succeeding or failing? Is there anything in the stderr > logs > > of the Oozie launcher? > > > > On Sun, Aug 6, 2017 at 4:36 AM, Ronald Green <green.ron...@gmail.com> > > wrote: > > > > > Hi! > > > > > > I have an HDP 1.3 (old, I know...) cluster that's running Pig 0.14 > > scripts > > > through Oozie. > > > > > > There's a rare nuisance that's driving me crazy - the last few lines > inin > > > the oozie pig launcher log state that pig started a map reduce job (or > > > several) and is keeping track of their progress and it ends there. The > > > thing is that the m/r jobs are already done but Pig is not aware of > that > > > and so it doesn't proceed to the next m/r jobs in the chain or ends the > > > process because the last m/r job executed. > > > > > > Looking at the cluster metrics doesn't show any problem at the cluster > > > (i.e. job tracker, task trackers and hdfs are all on and they haven't > > > failed while the pig action was running). > > > > > > Any idea how to get to the bottom of this? > > > > > > Thanks! > > > Ron > > > > > >
