hadoop-yarn-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Varun Saxena (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (YARN-5626) Support long running apps handling multiple flows
Date Thu, 08 Sep 2016 04:21:21 GMT

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

Varun Saxena commented on YARN-5626:
------------------------------------

As discussed in call we can still serve this use case by allowing flow context information
to be passed in TimelineEntity and take it if supplied to make writes to different tables.

But we also need to devise a mechanism to distribute writes to different collectors for such
a use case.

This JIRA has been opened with the intention to discuss more on this.

> Support long running apps handling multiple flows
> -------------------------------------------------
>
>                 Key: YARN-5626
>                 URL: https://issues.apache.org/jira/browse/YARN-5626
>             Project: Hadoop YARN
>          Issue Type: Sub-task
>          Components: timelineserver
>            Reporter: Varun Saxena
>            Assignee: Varun Saxena
>
> Many applications which can potentially use ATS have one or a few long running AMs' which
handle multiple tasks or serve multiple queries. As ATS scopes everything within an app, its
not possible for us to differentiate different flows.
> Moreover, all entities will be written to one or very few node collectors as writers
are distributed based on app



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