Hi Supreet, What does the coord job FAILED means? Was there any coord action created? Or it failed before that.
What is value of 'initialInstance'? If possible , can you please provide some log from the coord job UI? Regards, Mohammad On Tuesday, July 1, 2014 11:05 PM, Shwetha GS <[email protected]> wrote: instance in input and output events should use the EL functions as documented in http://oozie.apache.org/docs/4.0.1/CoordinatorFunctionalSpec.html#a6.6._Parameterization_of_Dataset_Instances_in_Input_and_Output_Events. Thats probably the reason for failure You can change log level by changing the following conf log4j.logger.org.apache.oozie=INFO, oozie INFO can be changed to DEBUG/TRACE for debugging On Tue, Jul 1, 2014 at 7:05 PM, Supreeth <[email protected]> wrote: > Hi Team: > > Setup a brand new oozie server and most of the usecases succeed. However > when I add a data check node into the coordinator on the likes of > > <datasets> > > <dataset name="raw-logs" frequency="${coord:minutes(1)}" > initial-instance="${initialInstance}" timezone="UTC"> > > > <uri-template>${nameNode}/${inputBaseDir}/${YEAR}${MONTH}${DAY}${HOUR}{MINUTE}</uri-template> > > </dataset> > > <dataset name="aggregated-logs" frequency="${coord:minutes(1)}" > initial-instance="${initialInstance}" timezone="U\ > TC"> > > > > <uri-template>/output-data/aggregator/aggregatedLogs/${YEAR}/${MONTH}/${DAY}/${HOUR}{MINUTE}</uri-template> > > </dataset> > > </datasets> > > <input-events> > > <data-in name="input" dataset="raw-logs"> > > <instance>2014-06-27T11:19Z</instance> > > </data-in> > > </input-events> > > <output-events> > > <data-out name="output" dataset="aggregated-logs"> > > <instance>2014-06-27T11:19Z</instance> > > </data-out> > > </output-events> > > The COORD app fails with status set to "FAILED". Not much in the logs on > the Oozie UI or in the oozie.log.dir. > > Any help to debug this further, how I can get more logging enabled which > can provide info on why the coord is getting marked as "failed"? > > Build info: > Oozie client build version: 4.0.0.2.1.2.1-471 > > oozie-log4j file: > > log4j.logger.openjpa=ALL, openjpa > log4j.logger.oozieops=ALL, oozieops > log4j.logger.oozieinstrumentation=ALL, oozieinstrumentation > log4j.logger.oozieaudit=ALL, oozieaudit > log4j.logger.org.apache.oozie=ALL, oozie > log4j.logger.org.apache.hadoop=ALL, oozie > > Thanks, > Supreeth > -- _____________________________________________________________ The information contained in this communication is intended solely for the use of the individual or entity to whom it is addressed and others authorized to receive it. It may contain confidential or legally privileged information. If you are not the intended recipient you are hereby notified that any disclosure, copying, distribution or taking any action in reliance on the contents of this information is strictly prohibited and may be unlawful. If you have received this communication in error, please notify us immediately by responding to this email and then delete it from your system. The firm is neither liable for the proper and complete transmission of the information contained in this communication nor for any delay in its receipt.
