hadoop-yarn-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Sunil G (JIRA)" <j...@apache.org>
Subject [jira] [Comment Edited] (YARN-5378) Accommodate app-id->cluster mapping
Date Tue, 17 Jan 2017 09:22:26 GMT

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

Sunil G edited comment on YARN-5378 at 1/17/17 9:21 AM:
--------------------------------------------------------

bq.Arguably user may have a static list of clusters. And that can be configurable at the client
side (UI end).
I do not feel that may be correct/useful. In case of ephemeral clusters, it can come up any
point of time. On such events, UI cannot make a configurable list of clusters. ATS could expose
an api to give the cluster IDs. This can be used by UI/any client for subsequent queries.


was (Author: sunilg):
bq.Arguably user may have a static list of clusters. And that can be configurable at the client
side (UI end).
I do not feel that may be correct/useful. In case of ephemeral clusters, it can come up any
point of time. On such events, UI cannot make a configurable list if list of clusters. ATS
could expose an api to give the cluster IDs which can be used by UI/any client.

> 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


Mime
View raw message