We don't use PurgeService to purge databases. We have our own purging script to
do that.
We run it daily.
Below is coord action purging section. Once you have purged coord actions, you
can also purge corresponding wf and wf_actions rows.
lcoordactionscursql :=
'SELECT ID
FROM '
|| lschemaname
|| '.coord_actions
WHERE status IN (''SUCCEEDED'', ''FAILED'',
''KILLED'',''TIMEDOUT'', ''IGNORED'')
AND last_modified_time < '
|| 'trunc(current_date - interval '''
|| lcutoffdays
|| ''' day(3) )';
lorph_coordactionscursql :=
'SELECT actions.ID FROM '
|| lschemaname
|| '.coord_actions actions, '
|| lschemaname
|| '.coord_jobs jobs WHERE actions.job_id = jobs.id(+) and jobs.id
is null';
From: Shwetha Shivalingamurthy <[email protected]>
To: "[email protected]" <[email protected]>
Sent: Thursday, August 13, 2015 10:35 PM
Subject: Re: Manually purging actions of long running coordinators
Yes, you can delete the actions from COORD_ACTIONS table. This will not
affect coord execution.
However, there is an API/command that gets the status of coord actions.
This API also has offset parameter. This offset will be offset wrt the
actions in the DB. From the end users¹s perspective(if anyone is using),
they will not know what actions are in DB and hence they will not be able
to use the offset parameter. We added filter on nominal time in the later
releases. You should upgrade to recent releases.
Regards,
Shwetha
On 14/08/15 6:26 am, "Ravuri, Venkata Puneet" <[email protected]> wrote:
>Hi,
>
>We use Oozie 3.2.0 and have many long running coordinators. The
>COORD_ACTIONS table has grown significantly.
>Oozie's PurgeService doesn't purge actions of running coordinators.
>
>Is it safe to manually purge these actions from COORD_ACTIONS table?
>Is there any recommended way to purge this table entries manually?
>I see that this issue is fixed in version 4.1.0
>(https://issues.apache.org/jira/browse/OOZIE-1532)
>
>
>Thanks and Regards,
>Puneet
>
