Hi Karthick, Few questions: * Which ooze version are you using? * Are you using mysql or oracle? * The slowness is shown in Oozie UI only. Did you try the command line :oozie job -info <COORD-ID-RETURNED> ? Is it slow in responding? * How many jobs are there in the DB? Does the old records are purged from DB?
Regards, Mohammad ----- Original Message ----- From: Karthick S <[email protected]> To: [email protected] Cc: Sent: Tuesday, October 30, 2012 11:34 AM Subject: Oozie becomes slow and it takes long time to schedule a job Hi All, We are facing some performance issue in oozie. we have a workflow configured which will be invoked by coordinator in specific intervals. But the coordinator job is not starting immediately. In oozie.log i could see coordinator job gets submitted and the coordinator xml contents. The coordinator id appears in the oozie web console after 1 hour. The system is under significant load. I am new to this oozie and trying to debug this issue. Can someone please point out further actions? Regards, Karthick
