Hi Eduardo, If your coordinators are triggering workflows every 3 minutes, and your workflows contain many actions, then i'm not surprised to see many entries in the database. Depending on your use case, you may consider reducing the frequency of the coordinator materialisation - e.g. trigger workflows every 10 minutes and just have them process more data each time. Can you provide any more detail on what your workflows are doing?
Also consider tweaking the PurgeService settings in oozie-site.xml. The PurgeService deletes completed workflows / coordinator / bundle jobs from the database. By default it runs every hour and deletes workflows older than 30 days and coordinator / bundle jobs older than 7 days. You could reduce the retention period to keep the database cleaner. However, this should not affect the UI so you may have DB contention. You can try increasing the oozie.service.JPAService.pool.max.active.conn property to say 20 to allow more connections back to MySQL to see if it helps. Thanks. On 20 Sep 2012, at 12:12, Eduardo Afonso Ferreira wrote: > Hi there, > > I have several coordinators that launch workflow jobs/actions as frequent as > every 3 minutes as long as there's room for it (concurrency set to 2 per > coordinator). At the end of the day, the Oozie database (MySQL) has thousands > of rows in WF_JOBS and WF_ACTIONS. After running Oozie for several days, I > see currently around 100K rows in each table. > > > I noticed that the web console becomes significantly slow after a while. > Does it have to do with the number of jobs/actions in the database? > Does it affect the performance of the jobs or just the UI? > Anything I can do to improve that? > > Thank you. > Eduardo.
