as mohammad says, oozie 2 has issues in its purge logic. still what you are seeing it is the expected behavior. no data of running jobs is deleted.
one way of solving this is to have back to back coord jobs every few months. then the completed ones will qualify for purging. thx Alejandro (phone typing) On May 28, 2013, at 20:07, Mohammad Islam <[email protected]> wrote: > Yes that is bug in 2.3.3. > You will need to delete those manually from the table. > > Regards, > Mohammad > > > > ________________________________ > From: The Trainer <[email protected]> > To: "[email protected]" <[email protected]> > Sent: Tuesday, May 28, 2013 7:48 PM > Subject: Oozie 2.3.2 - Long running coordinators - purge service not deleting > historical actions > > > Hi All, > > I am using Oozie 2.3.2 and I have more than 5 different coordinator jobs > running concurrently for 1 year duration. > > Found that Purge service is not deleting already SUCCESSFUL Coordinator > Action table records if COORD_ACTIONS parent Coordinator job is still in > RUNNING status. > > Any remedy for this? > > There are so many records getting created in COORD_ACTIONS table because o > above different coordinator jobs. > > Thanks,
