You're right, it might be other problem. I'm biased a little.
Granted that it's not caused by hive-exec(failures are from quite simple
queries), It might be disk full or network problem. But it was like that,
it might be detected by operation team in Cloudera.
Regard my suggestion as a cheap shot before doing some serious work.
Thanks.
2014-01-28 Xuefu Zhang <xzh...@cloudera.com>
> Thanks, Navis.
>
> Just curious, how are we sure that the task failure is caused by memory
> issue? In other work, did you see OOM in any task log?
>
> I think you are right, but just like to confirm.
>
> Thanks,
> Xuefu
>
>
> On Mon, Jan 27, 2014 at 6:44 PM, Navis류승우 <navis....@nexr.com> wrote:
>
> > Including HIVE-6259, HIVE-6310, etc., recent test failures of minimr
> tests
> > are seemed to be related to memory issue (not all of them but mostly).
> >
> > {noformat}
> > java.lang.Throwable: Child Error
> > at org.apache.hadoop.mapred.TaskRunner.run(TaskRunner.java:271)
> > Caused by: java.io.IOException: Task process exit with nonzero status of
> 1.
> > at org.apache.hadoop.mapred.TaskRunner.run(TaskRunner.java:258)
> > {noformat}
> >
> > Currently we uses 4 datanode + 4 task tracker mini cluster. If we cannot
> > reserve more memory only for hive tests (it would be really appreciated
> if
> > it could be), should we use smaller mini cluster for pre-tests?
> >
>
