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-4696) EntityGroupFSTimelineStore to work in the absence of an RM
Date Mon, 22 Feb 2016 16:12:18 GMT

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

Steve Loughran commented on YARN-4696:
--------------------------------------

filed HADOOP-12831. I know I could avoid suffering by bringing up a minidfs cluster, but don't
want to for two reasons

# It'll make tests significantly slower. Currently I'm only starting ATS, not YARN or HDFS.
# having ATS 1.5 not work in clusters where the FS isn't HDFS is effectively an incompatible
change. Not the fault of ATS though, more that local fs doesn't meet what you'd expect of
flush/hflush, and for small history logs, doesn't get happy

> 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, YARN-4696-003.patch, YARN-4696-005.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 0.0.0.0
> # disable retries on yarn client IPC; if it fails, tag app as unknown.



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

Mime
View raw message