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] [Updated] (YARN-4696) EntityGroupFSTimelineStore to work in the absence of an RM
Date Wed, 17 Feb 2016 19:08:18 GMT

     [ https://issues.apache.org/jira/browse/YARN-4696?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel

Steve Loughran updated YARN-4696:
    Attachment: YARN-4696-002.patch

Patch 002

# removes switch in exchange for making creation/use of RM something that can be subclassed
or mocked away
# switched to CompositeService for automatic handling of child service lifecycle; by adding
yarnclient & the others they get this lifecycle (and there are no need for special yarnClient!=null
checks anywhere in the code.
# also cleaned up the {{cacheItem.getStore().close()}} calls -I managed to get an NPE if the
store was null; they are services so can be handled via {{ServiceOperations}}

Finally: when the web API catches an illegal argument exception (or any other), the string
value is included. This helps track down problems like application ID conversion trouble in
your plugin, which would otherwise fail with no meaningful error messages or stack traces
either on the client or the server

> EntityGroupFSTimelineStore to work in the absence of an RM
> ----------------------------------------------------------
>                 Key: YARN-4696
>                 URL: https://issues.apache.org/jira/browse/YARN-4696
>             Project: Hadoop YARN
>          Issue Type: Sub-task
>          Components: timelineserver
>    Affects Versions: 2.8.0
>            Reporter: Steve Loughran
>            Assignee: Steve Loughran
>         Attachments: YARN-4696-001.patch, YARN-4696-002.patch
> {{EntityGroupFSTimelineStore}} now depends on an RM being up and running; the configuration
pointing to it. This is a new change, and impacts testing where you have historically been
able to test without an RM running.
> The sole purpose of the probe is to automatically determine if an app is running; it
falls back to "unknown" if not. If the RM connection was optional, the "unknown" codepath
could be called directly, relying on age of file as a metric of completion
> Options
> # add a flag to disable RM connect
> # skip automatically if RM not defined/set to
> # disable retries on yarn client IPC; if it fails, tag app as unknown.

This message was sent by Atlassian JIRA

View raw message