Hello ! After additionnal testing, it appears that the coordinators related to the workflows need to be stopped before workflow can be purged.
I thought that in Oozie 4.1 it was possible to purge worklows related to running coordinators. It seems I was wrong. May someone confirm this is attended behaviour in Oozie 4.1 please ? Best regards. Morgrim. Le 26 janv. 2016 10:14, "Morgrim Murdargent" <[email protected]> a écrit : > Hello ! > > I send you this ticket because I have a question related to oozie purge > service. > > I have an oozie 4.1.0 embedded with an HDP 2.2.4. > > I tried to activate the purge service by setting the following properties : > ### > oozie.service.PurgeService.older.than=30 > oozie.service.PurgeService.purge.interval=3600 > oozie.service.PurgeService.coord.older.than=5 > oozie.service.PurgeService.bundle.older.than=5 > oozie.service.PurgeService.purge.old.coord.action=true > oozie.service.PurgeService.purge.limit=100 > ### > > How can I check if the purge service is really doing the job ? Is this a > workflow launched by oozie ? Or is it internal database command ? > > The interval is set to 3600s but at which hour does it launch, at HH:00 ? > > BR. > > Morgrim > > >
