hadoop-yarn-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Joep Rottinghuis (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (YARN-5378) Accomodate app-id->cluster mapping
Date Fri, 13 Jan 2017 19:37:26 GMT

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

Joep Rottinghuis commented on YARN-5378:
----------------------------------------

[~rohithsharma] to solve your use-case we need two pieces: 1) schema change to accommodate
mapping. 2) Additional service that does the actual lookup. I think [~sjlee0] is tackling
1) as part of this jira, but not yet 2).

The same functionality is useful even in non-ephemeral clusters in environments with multiple
clusters and users not being aware of what runs where.

For any UI we'll have to determine what we do if there is a collision between app_ids on multiple
clusters. In that case the user would have to be presented with a choice. In the normal case
we can simply pick the first and only cluster and move on.

> Accomodate 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
>
> 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