You are viewing a plain text version of this content. The canonical link for it is here.
Posted to yarn-issues@hadoop.apache.org by "Li Lu (JIRA)" <ji...@apache.org> on 2016/09/30 18:28:20 UTC
[jira] [Updated] (YARN-5681) Change collector discovery to support
collectors mapped to clients but not applications
[ https://issues.apache.org/jira/browse/YARN-5681?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Li Lu updated YARN-5681:
------------------------
Attachment: YARN-5681-YARN-3359.001.patch
Upload a patch to extend collector representations in RMs and NMs. After this change, collectors are not solely mapped to applications, but can have more general mappings identified by collector ids. Collector id is a string and can be generated by some utility methods for app-level collectors.
The current patch is based on the latest YARN-3359 patch, which is based on YARN-5638. Any comments are more than welcome.
> Change collector discovery to support collectors mapped to clients but not applications
> ---------------------------------------------------------------------------------------
>
> Key: YARN-5681
> URL: https://issues.apache.org/jira/browse/YARN-5681
> Project: Hadoop YARN
> Issue Type: Sub-task
> Components: timelineserver
> Reporter: Li Lu
> Assignee: Li Lu
> Attachments: YARN-5681-YARN-3359.001.patch
>
>
> As discussed in YARN-3981, we need the service discovery mechanism to map collectors with their actual "ids", which may or may not be a concrete application Id. This JIRA proposes to generalize the concept of collector id in collector service discovery mechanism.
--
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