Mailing-List: contact yarn-issues-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: yarn-issues@hadoop.apache.org
Date: Mon, 22 Feb 2016 16:02:18 +0000 (UTC)
From: "Steve Loughran (JIRA)" <jira@apache.org>
To: yarn-issues@hadoop.apache.org
Message-ID: <JIRA.12939508.1455632637000.110433.1456156938237@Atlassian.JIRA>
In-Reply-To: <JIRA.12939508.1455632637000@Atlassian.JIRA>
References: <JIRA.12939508.1455632637000@Atlassian.JIRA>
 <JIRA.12939508.1455632637222@arcas>
Subject: [jira] [Commented] (YARN-4696) EntityGroupFSTimelineStore to work
 in the absence of an RM
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable


    [ https://issues.apache.org/jira/browse/YARN-4696?page=3Dcom.atlassian.=
jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=3D15157=
187#comment-15157187 ]=20

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

the next patch I put up will implement YARN-4716; you can use flush to trig=
ger a writeback.

Unfortunately =E2=80=94and this is not the fault of ATS=E2=80=94=C2=A0that =
doesn't work on file://, because that is a checksummed FS, and guess what b=
uffers things?

For tests we really need an easy way to turn checksum creation off from the=
 config; that can only be done today with accessors of the FS instance, and=
 that's unworkable

> 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 testin=
g 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 option=
al, 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)