[
https://issues.apache.org/jira/browse/YARN-2377?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14110221#comment-14110221
]
Gera Shegalov commented on YARN-2377:
-------------------------------------
Hi [~kasha], I considered {{StringUtils#stringifyException}} but discarded it
due to the following disadvantages:
# redundant deserialization of the exception object just for the sake of
serializing it right away
# as a consequence, hypothetically, when localization service runs as a
separate process with a dedicated classpath, we can encounter a
{{ClassNotFoundException}} during deserialization
> 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.2#6252)
