Figured out the problem. I had only Submitted the App and was not running it. So it was waiting for run command.
Thanks, On Thu, Jun 11, 2015 at 12:57 AM, Akash Mishra <[email protected]> wrote: > Hi Team, > > I am currently running oozie workflow using command line and job is stuck > in PREP state. WF_JOBS table has data for the given workflow id. But START > action is not getting triggered. > > WF_JOBS Record > # id, app_name, app_path, conf, created_time, end_time, external_id, > group_name, last_modified_time, log_token, parent_id, proto_action_conf, > run, sla_xml, start_time, status, user_name, wf_instance > '0000000-150610200637282-oozie-oozi-W', 'oozie-workshop-workflow-akash', > 'hdfs://<URL>:8020/user/akashm/workflow/workflow.xml', ?, '2015-06-10 > 20:12:12', NULL, NULL, NULL, '2015-06-10 20:12:12', '', NULL, ?, '0', ?, > NULL, 'PREP', 'akashm', ? > > > [image: Inline image 1] > > > Please let me know if you need any more details. I am running oozie > 4.0.0-cdh5.3.2. > > Also PFA tail of log. > > Can someone let me know which part of code search for the record in > WF_JOBS and perform action? > > -- > > Regards, > Akash Mishra. > > > "Its not our abilities that make us, but our decisions."--Albus Dumbledore > -- Regards, Akash Mishra. "Its not our abilities that make us, but our decisions."--Albus Dumbledore
