It looks like its happening in my collect method in my OutputCollector but
not seeing any stack trace. I put some debug logging in AbstractProcessor
and its failing here
while (hasNext()) {
try {
parse(nextLine(), output, reporter);
} catch (Throwable e) {
* log.info("Error parsing...."); *
e.printStackTrace();
saveChunkInError(e);
}
I see "Error parsing" and i can trace everything working in parse() up to
the line output.collect() so i imagine is failing there but not seeing any
stacktrace....
Is there a way to get all stderr/stdout to one logfile?
On Sat, Dec 10, 2011 at 10:21 PM, Eric Yang <[email protected]> wrote:
> In Mapreduce framework, everything that uses System.out or System.err
> are redirected automatically to syslog.
> You shouldn't need to do anything special.
>
> regards,
> Eric
>
> On Sat, Dec 10, 2011 at 7:07 PM, AD <[email protected]> wrote:
> > I have a custom processor in extraction/demux/processor/mapper do I need
> to
> > print something custom to stderr from there ?
> >
> >
> > On Sat, Dec 10, 2011 at 4:32 PM, Eric Yang <[email protected]> wrote:
> >>
> >> Hi AD,
> >>
> >> The stack trace is output to stdout of the mapreduce job. Hence,
> >> check the syslog file for the mapreduce job to find the actual cause
> >> of the problem. Hope this helps.
> >>
> >> regards,
> >> Eric
> >>
> >> On Sat, Dec 10, 2011 at 1:23 PM, AD <[email protected]> wrote:
> >> > i am seeing the following error :
> >> >
> >> > 2011-12-10 16:21:43,886 WARN btpool0-1 ChunkSaver - Unable to save a
> >> > chunk:
> >> > tags: testcluster - source:lilmac.home
> >> >
> >> > Is there a way to turn on more debugging to find out why?
> >
> >
>
