[
https://issues.apache.org/jira/browse/YARN-3477?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Steve Loughran updated YARN-3477:
---------------------------------
Affects Version/s: 2.6.0
Summary: TimelineClientImpl swallows exceptions (was:
TimelineClientImpl swallows root cause of retry failures)
{{TimelineClientImpl}} also catches InterruptedExceptions and either
# converts to IOE & so making it potentially treated as a retry
# during a sleep(), it will catch and discard.
Issue #2 means it is impossible to to reliably interrupt a thread which is in
the attempt-and-retry process of trying to talk to a non-responsive ATS
instance. While this does not impact normal operations, it does make it hard to
shut down threads talking to ATS
> 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
>
> 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)
