Hi Shouvanik Haldar, You might be havig hdfs:// as prefix in your Job Tracker URL.
Yesterday I had the similar issue and found that my Job Tracker URL has above said prefix. Once I removed it worked. Also check in OOzie UI - System Info page - Job Tracker Whitelist property. I found out my Job Tracker Host name with 8021 port number does exists but still I got below error. This error I got before removing the hdfs:// After removal it worked. Mohammad Islam <[email protected]>SubjectRe: Oozie 2.3.2 - Long running coordinators - purge service not deleting historical actionsDateWed, 29 May 2013 08:53:15 GMT Hi , No never used talented. Is there any value for property (oozie.service.HadoopAccessorService.nameNode.whitelist) in conf/ooze-site.xml? Regards, Mohammad ________________________________ From: "[email protected]" <[email protected]> To: [email protected] Sent: Tuesday, May 28, 2013 10:45 PM Subject: RE: Oozie 2.3.2 - Long running coordinators - purge service not deleting historical actions Has anyone ever faced a problem like below [2013-05-28 14:25:01]Deploying job to Hadoop... [2013-05-28 14:32:50]Deployment complete! [2013-05-28 14:33:01]Error submitting workflow job to Oozie. [2013-05-28 14:33:01]Please check if the "Job tracker end point" and "Oozie end point" are valid! [2013-05-28 14:33:01]E0901. E0901: Namenode [pofmv1145] not allowed, not in Oozies whitelist Has anybody used OOZIE with Talend? Regards, Shouvanik
