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

Gera Shegalov commented on YARN-2377:
-------------------------------------

Hi [~Naganarasimha], there is no deserialization in a sense of converting bytes 
to the original exception class. This fields are already strings in 
yarn_protos.proto:
{code}
 33 message SerializedExceptionProto {                                          
    
 34   optional string message = 1;                                              
    
 35   optional string trace = 2;                                                
    
 36   optional string class_name = 3;                                           
    
 37   optional SerializedExceptionProto cause = 4;                              
    
 38 }
{code}

> Localization exception stack traces are not passed as diagnostic info
> ---------------------------------------------------------------------
>
>                 Key: YARN-2377
>                 URL: https://issues.apache.org/jira/browse/YARN-2377
>             Project: Hadoop YARN
>          Issue Type: Improvement
>          Components: nodemanager
>    Affects Versions: 2.4.0
>            Reporter: Gera Shegalov
>            Assignee: Gera Shegalov
>         Attachments: YARN-2377.v01.patch
>
>
> In the Localizer log one can only see this kind of message
> {code}
> 14/07/31 10:29:00 INFO localizer.ResourceLocalizationService: DEBUG: FAILED { 
> hdfs://ha-nn-uri-0:8020/tmp/hadoop-yarn/staging/gshegalov/.staging/job_1406825443306_0004/job.jar,
>  1406827248944, PATTERN, (?:classes/|lib/).* }, java.net.UnknownHos 
> tException: ha-nn-uri-0
> {code}
> And then only {{ java.net.UnknownHostException: ha-nn-uri-0}} message is 
> propagated as diagnostics.



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

Reply via email to