Look for the following config properties
oozie.service.PurgeService.older.than
oozie.service.PurgeService.purge.interval




On 6/25/14, 3:12 AM, "[email protected]"
<[email protected]> wrote:

>Hello !
>
>We migrated oozie RDBMS from Derby to Postgres.
>We have a problem with workflows filling the partition where the oozie
>database is. (in 6 hours because there is a lot of workflows)
>I would like to know what I can purge in the database oozie to free some
>discspace ?
>
>In fact, I would love to know if there is a documentation concerning how
>the oozie database works.
>
>Here are the list of tables :
>bundle_actions
>bundle_jobs
>coord_actions
>coord_jobs
>oozie_sys
>openjpa_sequence_table
>sla_events
>sla_registration
>sla_summary
>validate_conn
>wf_actions
>wf_jobs
>
>If I want to remove old workflows from the database, may I do something
>like this :
>delete from WF_ACTIONS where job_id in (select id from WF_JOBS where
>created_time < @date);
>delete from WF_JOBS where created_time < @date;
>
>Best regards.
>
>Gwenael Le Barzic
>
>__________________________________________________________________________
>_______________________________________________
>
>Ce message et ses pieces jointes peuvent contenir des informations
>confidentielles ou privilegiees et ne doivent donc
>pas etre diffuses, exploites ou copies sans autorisation. Si vous avez
>recu ce message par erreur, veuillez le signaler
>a l'expediteur et le detruire ainsi que les pieces jointes. Les messages
>electroniques etant susceptibles d'alteration,
>Orange decline toute responsabilite si ce message a ete altere, deforme
>ou falsifie. Merci.
>
>This message and its attachments may contain confidential or privileged
>information that may be protected by law;
>they should not be distributed, used or copied without authorisation.
>If you have received this email in error, please notify the sender and
>delete this message and its attachments.
>As emails may be altered, Orange is not liable for messages that have
>been modified, changed or falsified.
>Thank you.
>

Reply via email to