hadoop-yarn-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Steve Loughran (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (YARN-3477) TimelineClientImpl swallows exceptions
Date Tue, 05 May 2015 15:22:00 GMT

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

Steve Loughran commented on YARN-3477:
--------------------------------------

-How about log @ debug except for that final rethrow event, when log @ info or even warn.
-Runtime vs IOE. I'd prefer IOException, we'd just need to update the tests and tag it as
incompatible. If we retain the text then anything catching an exception and looking for the
text would work from 2.6+

> TimelineClientImpl swallows exceptions
> --------------------------------------
>
>                 Key: YARN-3477
>                 URL: https://issues.apache.org/jira/browse/YARN-3477
>             Project: Hadoop YARN
>          Issue Type: Bug
>          Components: timelineserver
>    Affects Versions: 2.6.0, 2.7.0
>            Reporter: Steve Loughran
>            Assignee: Steve Loughran
>         Attachments: YARN-3477-001.patch, YARN-3477-002.patch
>
>
> If timeline client fails more than the retry count, the original exception is not thrown.
Instead some runtime exception is raised saying "retries run out"
> # the failing exception should be rethrown, ideally via NetUtils.wrapException to include
URL of the failing endpoing
> # Otherwise, the raised RTE should (a) state that URL and (b) set the original fault
as the inner cause



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

Mime
View raw message