Mailing-List: contact yarn-issues-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Date: Tue, 17 Jan 2017 09:36:26 +0000 (UTC)
From: "Rohith Sharma K S (JIRA)" <jira@apache.org>
To: yarn-issues@hadoop.apache.org
Message-ID: <JIRA.12989369.1468481292000.25676.1484645786793@Atlassian.JIRA>
In-Reply-To: <JIRA.12989369.1468481292000@Atlassian.JIRA>
References: <JIRA.12989369.1468481292000@Atlassian.JIRA> <JIRA.12989369.1468481292201@jira-lw-us.apache.org>
Subject: [jira] [Commented] (YARN-5378) Accommodate app-id->cluster mapping
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
archived-at: Tue, 17 Jan 2017 09:36:41 -0000


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

Rohith Sharma K S commented on YARN-5378:
-----------------------------------------

[~varun_saxena] I think  you misunderstood the use case. In cloud, clusters are arbitrarily spin up and destroyed. Each cluster has its own Id which UI never knows about it. To all those newly spin up cluster, same UI is being used. Admin can select the clusterId and navigate to any pages. So, it is worth to list ClusterId's from ATS rather than going with configuration model. 

> Accommodate app-id->cluster mapping
> -----------------------------------
>
>                 Key: YARN-5378
>                 URL: https://issues.apache.org/jira/browse/YARN-5378
>             Project: Hadoop YARN
>          Issue Type: Sub-task
>          Components: timelineserver
>            Reporter: Joep Rottinghuis
>            Assignee: Sangjin Lee
>              Labels: yarn-5355-merge-blocker
>         Attachments: YARN-5378-YARN-5355.01.patch, YARN-5378-YARN-5355.02.patch, YARN-5378-YARN-5355.03.patch
>
>
> In discussion with [~sjlee0], [~vrushalic], [~subru], and [~curino] a use-case came up to be able to map from application-id to cluster-id in context of federation for Yarn.
> What happens is that a "random" cluster in the federation is asked to generate an app-id and then potentially a different cluster can be the "home" cluster for the AM. Furthermore, tasks can then run in yet other clusters.
> In order to be able to pull up the logical home cluster on which the application ran, there needs to be a mapping from application-id to cluster-id. This mapping is available in the federated Yarn case only during the active live of the application.
> A similar situation is common in our larger production environment. Somebody will complain about a slow job, some failure or whatever. If we're lucky we have an application-id. When we ask the user which cluster they ran on, they'll typically answer with the machine from where they launched the job (many users are unaware of the underlying physical clusters). This leaves us to spelunk through various RM ui's to find a matching epoch in the application ID. 


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

---------------------------------------------------------------------
To unsubscribe, e-mail: yarn-issues-unsubscribe@hadoop.apache.org
For additional commands, e-mail: yarn-issues-help@hadoop.apache.org