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

Siddharth Seth commented on TEZ-519:
------------------------------------

Is this still a problem ?

> Misleading stack trace when using sessions
> ------------------------------------------
>
>                 Key: TEZ-519
>                 URL: https://issues.apache.org/jira/browse/TEZ-519
>             Project: Apache Tez
>          Issue Type: Bug
>            Reporter: Bikas Saha
>
> 13/09/27 12:43:00 INFO client.RMProxy: Connecting to ResourceManager at 
> /0.0.0.0:54311                                              
> 13/09/27 12:43:01 INFO examples.OrderedWordCount: Creating Tez Session        
>                                                       
> 13/09/27 12:43:01 INFO client.RMProxy: Connecting to ResourceManager at 
> /0.0.0.0:54311                                              
> 13/09/27 12:43:03 INFO impl.YarnClientImpl: Submitted application 
> application_1380218649569_0047 to ResourceManager at /0.0.0.0:54311           
>                                                                               
>                                           
> 13/09/27 12:43:03 INFO examples.OrderedWordCount: Created Tez Session         
>                                                       
> 13/09/27 12:43:03 INFO client.TezSession: Shutting down Tez Session, 
> sessionName=OrderedWordCountSession, 
> applicationId=application_1380218649569_0047                                  
>                                                                               
>   
> 13/09/27 12:43:03 INFO client.TezSession: Could not connect to AM, killing 
> session via YARN, sessionName=OrderedWordCountSession, 
> applicationId=application_1380218649569_0047                                  
>                                                         
> 13/09/27 12:43:03 INFO impl.YarnClientImpl: Killing application 
> application_1380218649569_0047                                      
> org.apache.hadoop.mapred.FileAlreadyExistsException: Output directory /out 
> already exists                                           
>         at 
> org.apache.tez.mapreduce.examples.OrderedWordCount.main(OrderedWordCount.java:357)
>                                        
>         at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)        
>                                                       
>         at 
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) 
>                                            
>         at 
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
>                                     
>         at java.lang.reflect.Method.invoke(Method.java:597)                   
>                                                       
>         at 
> org.apache.hadoop.util.ProgramDriver$ProgramDescription.invoke(ProgramDriver.java:72)
>                                     
>         at org.apache.hadoop.util.ProgramDriver.run(ProgramDriver.java:144)   
>                                                       
>         at 
> org.apache.tez.mapreduce.examples.ExampleDriver.main(ExampleDriver.java:79)   
>                                            
>         at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)        
>                                                       
>         at 
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) 
>                                            
>         at 
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
>                                     
>         at java.lang.reflect.Method.invoke(Method.java:597)                   
>                                                       
>         at org.apache.hadoop.util.RunJar.main(RunJar.java:212)                
>  



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Reply via email to