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 "Joep Rottinghuis (JIRA)" <ji...@apache.org> on 2016/07/11 17:21:19 UTC

[jira] [Updated] (YARN-3650) Consider concurrency situations for TimelineWriter

     [ https://issues.apache.org/jira/browse/YARN-3650?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Joep Rottinghuis updated YARN-3650:
-----------------------------------
    Labels: YARN-5355  (was: )

> Consider concurrency situations for TimelineWriter
> --------------------------------------------------
>
>                 Key: YARN-3650
>                 URL: https://issues.apache.org/jira/browse/YARN-3650
>             Project: Hadoop YARN
>          Issue Type: Sub-task
>          Components: timelineserver
>            Reporter: Vrushali C
>              Labels: YARN-5355
>
> [~jrottinghuis] brought up an interesting point in YARN-3411. Filing jira to track to discuss and handle the following: 
> For TimelineWriter and its implementations, is there an expectation set around
> concurrency? Is any synchronization expected / needed to ensure visibility when calls happen from different threads?
> How about entities, are they expected to be immutable once passed to the write method?
> Similarly for the constructor, we're assuming that the configuration object will not be modified while we're constructing a TimelineWriter?



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