tez-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Rohini Palaniswamy <rohini.adi...@gmail.com>
Subject Fwd: [jira] [Commented] (TEZ-917) NPE when executing running via a custom edge
Date Sat, 08 Mar 2014 07:41:09 GMT
Hi,
   Could you guys tell us what is the hive team using custom edges for?

Regards,
Rohini

---------- Forwarded message ----------
From: Siddharth Seth (JIRA) <jira@apache.org>
Date: Thu, Mar 6, 2014 at 10:24 AM
Subject: [jira] [Commented] (TEZ-917) NPE when executing running via a
custom edge
To: issues@tez.incubator.apache.org



    [
https://issues.apache.org/jira/browse/TEZ-917?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13922841#comment-13922841]

Siddharth Seth commented on TEZ-917:
------------------------------------

Scratch that. Looking at the trace, this is likely a race in the Hive
custom edge plugin..

> NPE when executing running via a custom edge
> --------------------------------------------
>
>                 Key: TEZ-917
>                 URL: https://issues.apache.org/jira/browse/TEZ-917
>             Project: Apache Tez
>          Issue Type: Bug
>            Reporter: Siddharth Seth
>
> Reported by [~vikram.dixit]. Likely a race in event routing.
> {code}
> java.lang.NullPointerException
>   at
org.apache.hadoop.hive.ql.exec.tez.CustomPartitionEdge.getNumSourceTaskPhysicalOutputs(CustomPartitionEdge.java:55)
>   at org.apache.tez.dag.app.dag.impl.Edge.getSourceSpec(Edge.java:183)
>   at
org.apache.tez.dag.app.dag.impl.VertexImpl.getOutputSpecList(VertexImpl.java:2371)
>   at
org.apache.tez.dag.app.dag.impl.TaskAttemptImpl.createRemoteTaskSpec(TaskAttemptImpl.java:518)
>   at
org.apache.tez.dag.app.dag.impl.TaskAttemptImpl$ScheduleTaskattemptTransition.transition(TaskAttemptImpl.java:1038)
>   at
org.apache.tez.dag.app.dag.impl.TaskAttemptImpl$ScheduleTaskattemptTransition.transition(TaskAttemptImpl.java:1027)
>   at
org.apache.hadoop.yarn.state.StateMachineFactory$SingleInternalArc.doTransition(StateMachineFactory.java:362)
>   at
org.apache.hadoop.yarn.state.StateMachineFactory.doTransition(StateMachineFactory.java:302)
>   at
org.apache.hadoop.yarn.state.StateMachineFactory.access$300(StateMachineFactory.java:46)
>   at
org.apache.hadoop.yarn.state.StateMachineFactory$InternalStateMachine.doTransition(StateMachineFactory.java:448)
>   at
org.apache.tez.dag.app.dag.impl.TaskAttemptImpl.handle(TaskAttemptImpl.java:721)
>   at
org.apache.tez.dag.app.dag.impl.TaskAttemptImpl.handle(TaskAttemptImpl.java:105)
>   at
org.apache.tez.dag.app.DAGAppMaster$TaskAttemptEventDispatcher.handle(DAGAppMaster.java:1432)
>   at
org.apache.tez.dag.app.DAGAppMaster$TaskAttemptEventDispatcher.handle(DAGAppMaster.java:1417)
>   at
org.apache.hadoop.yarn.event.AsyncDispatcher.dispatch(AsyncDispatcher.java:173)
>   at
org.apache.hadoop.yarn.event.AsyncDispatcher$1.run(AsyncDispatcher.java:106)
>   at java.lang.Thread.run(Thread.java:695)
> 2014-03-03 14:55:56,519 INFO [AsyncDispatcher event handler]
org.apache.hadoop.yarn.event.AsyncDispatcher: Exiting, bbye
> {code}



--
This message was sent by Atlassian JIRA
(v6.2#6252)

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message