[ 
https://issues.apache.org/jira/browse/HIVE-1422?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12894126#action_12894126
 ] 

Joydeep Sen Sarma commented on HIVE-1422:
-----------------------------------------

more hadoop goriness - i think John your fix was pretty spot on:

- there are three levels of job storage: 
   a. fully in memory (can get status and counters)
   b. partially in memory (a la retired - can get status and not counters)
   c. on disk (completed jobs)

so what is happening is that we are hitting case b. jobstatus is available - 
but not counters. we should probably anticipate the null jobstatus (which we 
used to get in 0.17 before b. and c. were available).

what is the effect of not having final counter values available in Hive? Local 
mode also doesn't report counters i think.

> skip counter update when RunningJob.getCounters() returns null
> --------------------------------------------------------------
>
>                 Key: HIVE-1422
>                 URL: https://issues.apache.org/jira/browse/HIVE-1422
>             Project: Hadoop Hive
>          Issue Type: Bug
>          Components: Query Processor
>    Affects Versions: 0.6.0
>            Reporter: John Sichi
>            Assignee: Joydeep Sen Sarma
>             Fix For: 0.7.0
>
>         Attachments: HIVE-1422.1.patch
>
>
> Under heavy load circumstances on some Hadoop versions, we may get a NPE from 
> trying to dereference a null Counters object.  I don't have a unit test which 
> can reproduce it, but here's an example stack from a production cluster we 
> saw today:
> 10/06/21 13:01:10 ERROR exec.ExecDriver: Ended Job = job_201005200457_701060 
> with exception 'java.lang.NullPointerException(null)'
> java.lang.NullPointerException
> at org.apache.hadoop.hive.ql.exec.Operator.updateCounters(Operator.java:999)
> at 
> org.apache.hadoop.hive.ql.exec.ExecDriver.updateCounters(ExecDriver.java:503)
> at org.apache.hadoop.hive.ql.exec.ExecDriver.progress(ExecDriver.java:390)
> at org.apache.hadoop.hive.ql.exec.ExecDriver.execute(ExecDriver.java:697)
> at org.apache.hadoop.hive.ql.exec.Task.executeTask(Task.java:107)
> at org.apache.hadoop.hive.ql.exec.TaskRunner.runSequential(TaskRunner.java:55)
> at org.apache.hadoop.hive.ql.exec.TaskRunner.run(TaskRunner.java:47)

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

Reply via email to