hadoop-yarn-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Li Lu (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (YARN-3545) Investigate the concurrency issue with the map of timeline collector
Date Tue, 18 Aug 2015 00:55:46 GMT

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

Li Lu commented on YARN-3545:
-----------------------------

Hi [~xgong], you're right that right now this critical section can only be accessed by the
AM and RM, and there's no concurrency for the same application id (unless I'm missing something,
which is possible :) ). The fix here is to be consistent with the original TimelineCollectorManager,
which has a synchronized map to store appId->collector mappings. We may want to preserve
this thread-safe semantic for collector managers for future usages.

Right now this patch is stale and I would personally assign it with a low priority.  

> Investigate the concurrency issue with the map of timeline collector
> --------------------------------------------------------------------
>
>                 Key: YARN-3545
>                 URL: https://issues.apache.org/jira/browse/YARN-3545
>             Project: Hadoop YARN
>          Issue Type: Sub-task
>            Reporter: Zhijie Shen
>            Assignee: Li Lu
>         Attachments: YARN-3545-YARN-2928.000.patch
>
>
> See the discussion in YARN-3390 for details. Let's continue the discussion here.



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

Mime
View raw message