Hi
We are seeing our map-reduce jobs crashing once in a while and have to go
through the logs on all the nodes to figure out what went wrong. Sometimes
it is low resources and sometimes it is a programming error which is
triggered on specific inputs.. Same is true for some of our hive queries.
We set a part of the failure reason as the diagnostic message for a
failed task that a JobClient API retrieves/can retrieve:
http://hadoop.apache.org/docs/current/api/org/apache/hadoop/mapred/RunningJob.html#getTaskDiagnostics(org.apache.hadoop.mapred.TaskAttemptID).
Often this is
'useless' given t
Harsh: thanks for the quick response.
we often see an error response such as "Failed(Query returned non-zero
code: 2, cause: FAILED: Execution Error, return code 2 from
org.apache.hadoop.hive.ql.exec.MapRedTask)" and then go through all the
logs to figure out what happened. I use the jobtracker U
You can get the stats for a job using rumen.
http://ksssblogs.blogspot.in/2013/06/getting-job-statistics-using-rumen.html
Regards,
Som Shekhar Sharma
+91-8197243810
On Tue, Aug 27, 2013 at 10:54 AM, Gopi Krishna M wrote:
> Harsh: thanks for the quick response.
>
> we often see an error respons
