[ 
https://issues.apache.org/jira/browse/PIG-3843?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Rohini Palaniswamy resolved PIG-3843.
-------------------------------------

    Resolution: Invalid

This was a bug in a particular revision of Tez and long fixed.

> Pig script encounters error with Tez MemoryDistributor
> ------------------------------------------------------
>
>                 Key: PIG-3843
>                 URL: https://issues.apache.org/jira/browse/PIG-3843
>             Project: Pig
>          Issue Type: Sub-task
>          Components: tez
>            Reporter: Rohini Palaniswamy
>             Fix For: tez-branch
>
>
> {code}
> 2014-03-26 21:53:58,851 [JobControl] INFO 
> org.apache.pig.backend.hadoop.executionengine.tez.TezJob - DAG Status:
> status=FAILED, progress=TotalTasks: 2677 Succeeded: 2589 Running: 0 Failed: 1
> Killed: 87, diagnostics=Vertex failed, vertexName=scope-4375,
> vertexId=vertex_1394493512142_18439_1_02, diagnostics=[Task failed,
> taskId=task_1394493512142_18439_1_02_000000,
> diagnostics=[AttemptID:attempt_1394493512142_18439_1_02_000000_0 Info:Error:
> java.lang.IllegalStateException: All inputs are expected to ask for memory
>         at
> com.google.common.base.Preconditions.checkState(Preconditions.java:145)
>         at
> org.apache.tez.runtime.common.resources.MemoryDistributor.makeInitialAllocations(MemoryDistributor.java:124)
>         at
> org.apache.tez.runtime.LogicalIOProcessorRuntimeTask.initialize(LogicalIOProcessorRuntimeTask.java:224)
>         at
> org.apache.hadoop.mapred.YarnTezDagChild$4.run(YarnTezDagChild.java:522)
>         at java.security.AccessController.doPrivileged(Native Method)
>         at javax.security.auth.Subject.doAs(Subject.java:415)
>         at
> org.apache.hadoop.security.UserGroupInformation.doAs(UserGroupInformation.java:1570)
>         at
> org.apache.hadoop.mapred.YarnTezDagChild.main(YarnTezDagChild.java:515)
> Features: GROUP_BY,FILTER,UNION
> {code}
> Trying to get a simple script to reproduce.



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

Reply via email to