HI Mohammad:
With the following changes also I see the same error.
<input-events>
<data-in name="coordInput0" dataset="input1">
<instance>${coord:current(0)}</instance>
</data-in>
</input-events>
log4j prop:
# XLogService sets its value to '${oozie.home}/logs'
log4j.logger.org.apache.oozie=DEBUG, oozie
log4j.appender.oozie=org.apache.log4j.DailyRollingFileAppender
log4j.appender.oozie.DatePattern='.'yyyy-MM-dd-HH
log4j.appender.oozie.File=${oozie.log.dir}/oozie.log
log4j.appender.oozie.Append=true
log4j.appender.oozie.layout=org.apache.log4j.PatternLayout
log4j.appender.oozie.layout.ConversionPattern=%d{ISO8601} %5p %c{1}:%L -
%m%n
oozie server start up has the following property :
-Doozie.log.dir=/var/log/oozie
No logging on UI or on any of the logs.
I think the larger issue is that logs might not be configured right due to
which the issue is difficult to debug. When the oozie server accepts a
coord job, does it write to any debug or trace lines? I dont see much added
in the oozie logs dir even with DEBUG or TRACE logging.
-S
On Wed, Jul 2, 2014 at 1:25 PM, Mohammad Islam <[email protected]>
wrote:
> Hi Supreet,
> So there is no log either in oozie.log or under "coord job log" tab of
> UI. right?
>
> I think there should be at least something.
>
> You said when you comment the following lines, it worked. right?
>
>
> <input-events>
> <data-in name="coordInput1" dataset="input1">
> <start-instance>${coord:current(0)}</start-instance>
> <end-instance>${coord:current(0)}</end-instance>
> </data-in>
> </input-events>
>
> In general, if there is only one instance, we use <instance> instead of
> start/end-instance. can you please try with this?
>
> Regards,
> Mohammad
>
>
>
>
>
>
> On Wednesday, July 2, 2014 12:27 PM, Supreeth <[email protected]>
> wrote:
>
>
>
> Thanks Shwetha, Mohammad for the response.
>
> Here is the coord xml - http://pastebin.com/xy6xgC1N
>
> I have enabled logging on the oozie server to DEBUG, but not much
> information in the logs.
>
> On the Oozie UI also there is not much information. The only info is the
> screen shot below and the coord moves to FAILED state immediately.
>
> However if I comment out the lines within input-events, the coord works
> fine. I do miss out on the data check functionality.
>
> start=2014-06-28T11:19Z
> end=2014-06-30T12:00Z
> initialInstance=2014-06-28T11:19Z
>
>
>
> Any help or pointers appreciated.
>
> -S
>
>
>
>
> On Wed, Jul 2, 2014 at 1:48 AM, Mohammad Islam <[email protected]>
> wrote:
>
>
> >
> >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.
>
