Support Questions
Find answers, ask questions, and share your expertise
Announcements
Alert: Welcome to the Unified Cloudera Community. Former HCC members be sure to read and learn how to activate your account here.

not able to schedule falcon feed

not able to schedule falcon feed

Guru

Team:

I am following http://hortonworks.com/blog/introduction-apache-falcon-hadoop/ link and trying to implement example 3 but I am not able to schedule feed entity. I am getting below error, I tried to check falcon_application.log file but unfortunately it is not getting generated.

s0998dnz@lxhdpmasttst001 falconReplicationDemo]$ falcon entity -type feed -schedule -name replication-feed

ERROR: Bad Request;default/org.apache.falcon.FalconWebException::org.apache.falcon.FalconException: Entity schedule failed for feed: replication-feed

4 REPLIES 4
Highlighted

Re: not able to schedule falcon feed

So you definitely need the falcon application log. It can be a million things ( for example the falcon staging/work/... folders not being there or having the right access rights )

So you mean no application log is there? under /var/log/falcon? We had this problem once after an upgrade when some log4j files where not copied to the new falcon config folder.

Highlighted

Re: not able to schedule falcon feed

We recently updated the following falcon tutorial to work with the 2.4 Sandbox.

http://hortonworks.com/hadoop-tutorial/defining-processing-data-end-end-data-pipeline-apache-falcon/

This has a more current perspective than the blog from 2014.

Highlighted

Re: not able to schedule falcon feed

Guru

@Rafael Coss: Do you have any updated doc for example 3 in http://hortonworks.com/blog/introduction-apache-falcon-hadoop/ old page.

Highlighted

Re: not able to schedule falcon feed

Guru

@Benjamin Leonhardi: Yes iI found logs and it was just a frequency error. Actually I was setting up frequency to 1 minute which is not a possible in falcon.

Now I am able to schedule and jobs are completing also but problem is data is not replicating from source's table to target table and there is not error in falcon/oozie logs.

Don't have an account?
Coming from Hortonworks? Activate your account here